Skip to content

Probe Bedrock and Vertex provider keys (ADR-0003 follow-up) #15

Open

Description

@johnnyhuy

Why

The current probe layer (src/main/probes/) only knows Anthropic. The catalog has 18 entries but probeProvider() returns error: No probe implemented for "<id>" for any provider whose probeKind is aws, gcp, or azure.

Bedrock and Vertex don't expose a cheap "validate this credential" HTTP endpoint the way OpenAI/Anthropic do — there's no /v1/models you can hit. The standard check is to call a tiny STS-shaped API and parse the response. Three axes:

  1. Bedrock — call bedrock:ListFoundationModels (or bedrock:ListCustomModels) with the user's AWS credentials (default chain). 403/expired token ≠ working.
  2. Vertex — call aiplatform.googleapis.com/v1/projects/<project>/locations/global/publishers/google/models with the configured ADC + project + region. The envKeys[] for Vertex is empty today so we need to surface a "Project + Region required" step in the wizard before this can be wired.
  3. Azure — GET <endpoint>/openai/deployments?api-version=2024-02-01 with the user's AZURE_OPENAI_API_KEY. Or just probe the deployment the user names.

Scope

  • Wire aws probe kind: uses SDK's default credential provider chain; minimal IAM sigv4 against bedrock-runtime or bedrock control plane; returns valid | error with the AWS error code surfaced in detail.
  • Wire gcp probe kind: takes a project and region from wizard config; uses @google-cloud/aiplatform or just an authenticated REST GET; requires gcloud auth application-default login upstream.
  • Wire azure probe kind (and azure-openai): simple GET against the deployment list with the configured key.
  • Vault entry for Vertex needs to carry {project, region} alongside the credential. Either widen SecretWriteOptions or surface project/region as separate UI fields in the Keys step.
  • Update PROVIDER_CATALOG notes for cloud_creds rows to indicate "wizard will ask for project/region first".
  • Renderer Keys step: when user picks Vertex, ask for project id + region before "Save"; persist into vault alongside the credential (or as a sibling secret).
  • App + CLI both pick up the same probes via the shared runProbe() dispatcher.

Acceptance criteria

  • runProbe({ providerId: 'bedrock' }) returns { valid: true, status: 'ok' } against a working AWS account with Bedrock access.
  • Same returns { valid: false, status: 'invalid', detail: 'AWS error: ...' } for an unconfigured credential chain.
  • Vertex probe requires a saved project + region; errors sensibly without one.
  • Azure probe works against an actual deployment.
  • All three appear in the Validate button in the renderer without code changes beyond the probe files.
  • Tests (or fixture-mocked HTTP) for at least the error paths.
  • npm run typecheck && npm run lint && npm run build clean.

References

Activity

  1. johnnyhuy commented on Nov 8, 2026

    @johnnyhuy
    ContributorAuthor

    Split for review size: the probe layer (src/main/probes/ aws/gcp/azure kinds, ProbeContext project/region, catalog notes, mocked-HTTP tests) is being worked as #47 on branch agent/issue-47-cloud-probes. The vault storage for Vertex {project, region} and the renderer Keys step fields stay on this issue for a later run. CLI parity in cli/src/lib/probes.ts will be a separate PR (independent release flow).

  2. johnnyhuy commented on Nov 8, 2026

    @johnnyhuy
    ContributorAuthor

    Progress from the work loop - the probe layer landed in #48 (closes #47), and the vault and renderer slice for Vertex project and region is up in #50 (closes #49). Still open on this issue - CLI probe parity in cli/src/lib/probes.ts as a separate CLI PR, and live-key verification against real Bedrock and Vertex accounts.

  3. johnnyhuy commented on Nov 8, 2026

    @johnnyhuy
    ContributorAuthor

    CLI probe parity landed in #52 (the CLI half of this issue, split out as #51). The app probe layer from #48, the vault wiring from #50 and the CLI dispatch now cover Bedrock, Vertex and Azure with mocked HTTP tests on both sides. What remains here needs live provider accounts: a Bedrock probe against a working AWS account, a Vertex probe against a real GCP project, and an Azure probe against a real deployment. Parking the live verification with this note rather than closing, since no agent run can supply those credentials.

  4. johnnyhuy commented on Nov 12, 2026

    @johnnyhuy
    ContributorAuthor

    The scheduled run rechecked origin/main at 93c2a42. The implementation slices are already merged in #48, #50 and #52. The remaining live-provider acceptance checks need Johnny or a reviewer with working cloud accounts. This run made no live provider calls and used no real credentials.

    Added needs-live-provider-verification so this issue is explicitly parked and stays open. Existing implementation limits still apply as recorded in #48 and #52: Bedrock reads environment credentials rather than the full AWS SDK default chain, and Vertex takes an access token rather than loading ADC itself. The checks below do not establish live-provider compatibility.

    Both repository gates passed against the exact origin/main commit.

    • mise run ci:app - exit 0; catalog check, typecheck, lint, all unit suites and the main/preload/renderer builds passed.
    • mise run ci:cli - exit 0; typecheck, 25 tests with 0 failures, and the Linux x64 compiled binary build passed.
    • git diff --check - exit 0; worktree clean after both gates.

    Representative proof from the app gate, using mocked HTTP only:

      ✓ aws no credentials returns invalid
      ✓ aws mocked 200 returns ok
      ✓ aws Authorization uses SigV4 credential scope
      ✓ aws mocked 403 returns invalid
      ✓ gcp missing project and region returns error
      ✓ gcp missing config makes no HTTP request
      ✓ gcp mocked 200 returns ok
      ✓ gcp request path carries project and region
      ✓ azure mocked 200 returns ok
      ✓ azure request sends the api-key header
      ✓ azure mocked 401 returns invalid
    all cloud probe cases passed
    all probe context cases passed
    all discovery cache cases passed
    ✓ built in 857ms
    

    The CLI gate passed aws mocked 200 returns ok and sends a SigV4 signed request, gcp mocked 200 returns ok with project and region in the path, azure missing endpoint returns error, mocked 200 validates, and the 16 discovery-cache fixture cases.

     25 pass
     0 fail
     105 expect() calls
    Ran 25 tests across 2 files.
    compile /tmp/hoist-test bun-linux-x64-v1.3.14
    

    No user-facing change, new commit or PR was needed in this run. The dependency install reported 23 audit findings (12 moderate, 9 high, 2 critical); no dependency versions were changed.

    Sweep completed with 0 merged PRs, 0 closed PRs, 0 remote branches deleted and 4 leftover local agent branches deleted after confirming their work had merged. Release PR #46 is excluded from the sweep. The schedule remains active because the exit condition requires a clear PR list and #46 is still open.

  5. johnnyhuy commented on Nov 13, 2026

    @johnnyhuy
    ContributorAuthor

    Scheduled run reverified origin/main at 93c2a42 on 13 November 2026. No user-facing change or new PR was needed. #16 and #17 are closed; this issue remains explicitly parked with needs-live-provider-verification.

    Both repository gates passed with exit 0.

    • mise run ci:app passed catalog freshness, typecheck, lint, all unit suites and main/preload/renderer builds.
    • mise run ci:cli passed typecheck, 25 tests with 0 failures and the Linux x64 compiled binary build.
    • git diff --check passed and the worktree remained clean.

    Representative proof from the app gate:

      ✓ aws no credentials returns invalid
      ✓ aws mocked 200 returns ok
      ✓ aws Authorization uses SigV4 credential scope
      ✓ aws mocked 403 returns invalid
      ✓ gcp missing config makes no HTTP request
      ✓ gcp mocked 200 returns ok
      ✓ gcp request path carries project and region
      ✓ azure mocked 200 returns ok
      ✓ azure request sends the api-key header
    all cloud probe cases passed
    all probe context cases passed
    all discovery cache cases passed
    ✓ built in 843ms
    

    CLI proof includes aws mocked 200 returns ok and sends a SigV4 signed request, gcp mocked 200 returns ok with project and region in the path, azure missing endpoint returns error, mocked 200 validates and all 16 discovery-cache fixture tests:

     25 pass
     0 fail
     105 expect() calls
    Ran 25 tests across 2 files.
    compile /tmp/hoist-test bun-linux-x64-v1.3.14
    

    No real cloud credentials were used and no live provider calls were made. Johnny or a reviewer with working cloud accounts still needs to perform the acceptance checks. Existing credential-source limits remain as recorded in #48 and #52.

    Sweep completed with 0 merged, 0 closed and 0 deleted branches. Only release PR #46 remains open and was excluded from the sweep. The schedule stays active because the exit condition requires a clear PR list.

    The app dependency install still reports 23 audit findings (12 moderate, 9 high, 2 critical). No dependencies were changed.

  6. johnnyhuy commented on Nov 13, 2026

    @johnnyhuy
    ContributorAuthor

    Reverified origin/main at 93c2a42 on 13 November 2026. No user-facing change or new PR was needed. The implementation is already merged in #48, #50 and #52; #16 and #17 are closed.

    Both repository gates passed with exit 0.

    • mise run ci:app passed catalog freshness, typecheck, lint, all unit suites and the main/preload/renderer builds.
    • mise run ci:cli passed typecheck, all 25 tests and the Linux x64 compiled binary build.
    • git diff --check passed; the worktree is clean.

    Representative app proof from mocked HTTP fixtures:

      ✓ aws mocked 200 returns ok
      ✓ aws Authorization uses SigV4 credential scope
      ✓ aws mocked 403 returns invalid
      ✓ gcp missing config makes no HTTP request
      ✓ gcp mocked 200 returns ok
      ✓ gcp request path carries project and region
      ✓ azure mocked 200 returns ok
      ✓ azure request sends the api-key header
    all cloud probe cases passed
    all probe context cases passed
    all discovery cache cases passed
    ✓ built in 919ms
    

    CLI proof includes aws mocked 200 returns ok and sends a SigV4 signed request, gcp mocked 200 returns ok with project and region in the path, azure missing endpoint returns error, mocked 200 validates and all 16 discovery-cache fixture tests.

     25 pass
     0 fail
     105 expect() calls
    Ran 25 tests across 2 files.
    compile /tmp/hoist-test bun-linux-x64-v1.3.14
    

    No real provider credentials or live provider calls were used. This issue stays parked with needs-live-provider-verification until Johnny or a reviewer can perform the live acceptance checks. Existing credential-source limits remain as recorded in #48 and #52.

    Sweep completed with 0 merged PRs, 0 closed PRs and 0 deleted branches. Only release PR #46 remains open and was excluded from the sweep. The schedule stays active because the exit condition requires a clear PR list. No release commands were run.

    The app dependency install still reports 23 audit findings (12 moderate, 9 high, 2 critical). No dependencies were changed.

  7. johnnyhuy commented on Nov 13, 2026

    @johnnyhuy
    ContributorAuthor

    Scheduled run verified origin/main at 93c2a420c5c1e63f687e64f1cf0681b14b7dfaf2 on 13 November 2026. No user-facing change or new PR was needed. #16 and #17 are closed; #15 stays parked with needs-live-provider-verification for Johnny or a reviewer with cloud accounts.

    Both repository gates passed with exit 0.

    • mise run ci:app passed catalog freshness, typecheck, lint, all unit suites and the main/preload/renderer builds.
    • mise run ci:cli passed typecheck, 25 tests and the Linux x64 compiled binary build.
    • git diff --check passed and the worktree is clean.

    Representative proof from the app gate, using mocked responses only:

      ✓ aws mocked 200 returns ok
      ✓ aws Authorization uses SigV4 credential scope
      ✓ aws mocked 403 returns invalid
      ✓ gcp missing config makes no HTTP request
      ✓ gcp mocked 200 returns ok
      ✓ gcp request path carries project and region
      ✓ azure mocked 200 returns ok
      ✓ azure request sends the api-key header
    all cloud probe cases passed
    all probe context cases passed
    all discovery cache cases passed
    ✓ built in 938ms
    

    CLI proof includes aws mocked 200 returns ok and sends a SigV4 signed request, gcp mocked 200 returns ok with project and region in the path, azure missing endpoint returns error, mocked 200 validates, and the discovery-cache fixture tests.

     25 pass
     0 fail
     105 expect() calls
    Ran 25 tests across 2 files.
    compile /tmp/hoist-test bun-linux-x64-v1.3.14
    

    No real provider credentials or live provider calls were used. Credential-source limitations remain as previously recorded: Bedrock reads environment credentials rather than the full SDK default chain; Vertex takes an access token rather than loading ADC itself.

    Sweep completed with 0 merged PRs, 0 closed PRs and 0 deleted branches. Only release PR #46 remains open and was excluded. The schedule stays active because the exit condition requires a clear PR list. No release commands were run.

    The app install reported the existing 23 dependency audit findings (12 moderate, 9 high, 2 critical). No dependency versions were changed.

  8. johnnyhuy commented on Nov 13, 2026

    @johnnyhuy
    ContributorAuthor

    Reverified origin/main at 93c2a420c5c1e63f687e64f1cf0681b14b7dfaf2 on 13 November 2026. No user-facing change or new PR was needed. This issue remains parked pending live-provider checks by Johnny or a reviewer with working cloud accounts.

    Both repository gates passed with exit 0.

    • mise run ci:app passed catalog freshness, typecheck, lint, all unit suites and main/preload/renderer builds.
    • mise run ci:cli passed typecheck, all 25 tests and the Linux x64 compiled binary build.
    • git diff --check passed and the worktree is clean.

    Representative app proof from mocked HTTP fixtures:

      ✓ aws mocked 200 returns ok
      ✓ aws Authorization uses SigV4 credential scope
      ✓ aws mocked 403 returns invalid
      ✓ gcp missing config makes no HTTP request
      ✓ gcp mocked 200 returns ok
      ✓ gcp request path carries project and region
      ✓ azure mocked 200 returns ok
      ✓ azure request sends the api-key header
    all cloud probe cases passed
    all probe context cases passed
    all discovery cache cases passed
    ✓ built in 998ms
    

    CLI proof includes aws mocked 200 returns ok and sends a SigV4 signed request, gcp mocked 200 returns ok with project and region in the path, azure missing endpoint returns error, mocked 200 validates and all 16 discovery-cache fixture cases.

     25 pass
     0 fail
     105 expect() calls
    Ran 25 tests across 2 files.
    compile /tmp/hoist-test bun-linux-x64-v1.3.14
    

    No real credentials or live provider calls were used. The previously documented credential-source limits remain. Implementation PRs #48, #50 and #52 are merged.

    Sweep completed with 0 merged PRs, 0 closed PRs and 2 stale local agent branches deleted after confirming they were ancestors of origin/main. Release PR #46 remains excluded from the sweep. The schedule remains active because the exit condition requires a clear PR list. No release commands were run.

    The app dependency install reported 23 audit findings (12 moderate, 9 high, 2 critical). No dependencies were changed.

  9. johnnyhuy commented on Nov 13, 2026

    @johnnyhuy
    ContributorAuthor

    Reverified origin/main at 93c2a420c5c1e63f687e64f1cf0681b14b7dfaf2 on 13 November 2026. No user-facing change or new PR was needed.

    • mise run ci:app passed with exit 0, including catalog freshness, typecheck, lint, all unit suites and the app builds.
    • mise run ci:cli passed with exit 0, including typecheck, 25 tests, 0 failures and the Linux x64 binary build.
    • git diff --check passed and the worktree stayed clean.

    Mocked provider proof from the gates:

      ✓ aws mocked 200 returns ok
      ✓ aws Authorization uses SigV4 credential scope
      ✓ aws mocked 403 returns invalid
      ✓ gcp missing config makes no HTTP request
      ✓ gcp mocked 200 returns ok
      ✓ gcp request path carries project and region
      ✓ azure mocked 200 returns ok
      ✓ azure request sends the api-key header
    all cloud probe cases passed
    all probe context cases passed
    all discovery cache cases passed
    
     25 pass
     0 fail
     105 expect() calls
    Ran 25 tests across 2 files.
    compile /tmp/hoist-test bun-linux-x64-v1.3.14
    

    No live provider calls or real credentials were used. This issue remains parked for a reviewer with working cloud accounts; the previously documented credential-source limitations remain.

    Sweep completed with 0 merged, 0 closed and 0 branches deleted. Release PR #46 remains excluded. The schedule stays active because the pause condition requires a clear PR list. No release commands were run.

  10. johnnyhuy commented on Nov 13, 2026

    @johnnyhuy
    ContributorAuthor

    Reverified origin/main at 93c2a420c5c1e63f687e64f1cf0681b14b7dfaf2 on 14 November 2026. No user-facing change, commit or new PR was needed; the implementation slices are already merged.

    • mise run ci:app passed with exit 0, covering catalog freshness, typecheck, lint, all unit suites and the main/preload/renderer builds.
    • mise run ci:cli passed with exit 0, covering typecheck, 25 tests with 0 failures and the Linux x64 compiled binary build.
    • git diff --check passed; the worktree stayed clean.

    Representative proof from mocked provider tests:

      ✓ aws mocked 200 returns ok
      ✓ aws Authorization uses SigV4 credential scope
      ✓ aws mocked 403 returns invalid
      ✓ gcp missing config makes no HTTP request
      ✓ gcp mocked 200 returns ok
      ✓ gcp request path carries project and region
      ✓ azure mocked 200 returns ok
      ✓ azure request sends the api-key header
    all cloud probe cases passed
    all probe context cases passed
    all discovery cache cases passed
    
     25 pass
     0 fail
     105 expect() calls
    Ran 25 tests across 2 files.
    compile /tmp/hoist-test bun-linux-x64-v1.3.14
    

    No real credentials or live provider calls were used. #15 remains parked with needs-live-provider-verification for Johnny or a reviewer with cloud accounts. The existing credential-source limits remain: Bedrock reads environment credentials rather than the full SDK default chain; Vertex takes an access token rather than loading ADC itself.

    Sweep completed with 0 merged PRs, 0 closed PRs and 0 branches deleted. Release PR #46 remains excluded; the schedule stays active because the pause condition requires a clear PR list. No release commands were run. The app dependency install reported the existing 23 audit findings; no dependencies were changed.

  11. johnnyhuy commented on Nov 13, 2026

    @johnnyhuy
    ContributorAuthor

    Verified origin/main at 93c2a420c5c1e63f687e64f1cf0681b14b7dfaf2 on 14 November 2026. No user-facing change, commit or PR was needed; #16 and #17 are closed and this issue remains parked with needs-live-provider-verification.

    Both repository gates passed with exit 0.

    • mise run ci:app passed catalog freshness, typecheck, lint, all unit suites and main/preload/renderer builds.
    • mise run ci:cli passed typecheck, all 25 tests with 0 failures and the Linux x64 compiled binary build.
    • git diff --check passed and the worktree stayed clean.

    Representative mocked-response proof from this run:

      ✓ aws mocked 200 returns ok
      ✓ aws Authorization uses SigV4 credential scope
      ✓ aws mocked 403 returns invalid
      ✓ gcp missing config makes no HTTP request
      ✓ gcp mocked 200 returns ok
      ✓ gcp request path carries project and region
      ✓ azure mocked 200 returns ok
      ✓ azure request sends the api-key header
    all cloud probe cases passed
    all probe context cases passed
    all discovery cache cases passed
    
     25 pass
     0 fail
     105 expect() calls
    Ran 25 tests across 2 files.
    compile /tmp/hoist-test bun-linux-x64-v1.3.14
    

    No live provider calls or real credentials were used. Johnny or a reviewer with cloud accounts still needs to perform the live acceptance checks. The existing credential-source limitations remain as recorded in #48 and #52.

    Sweep completed with 0 merged PRs, 0 closed PRs and 1 stale local agent branch deleted after confirming it was an ancestor of origin/main. Release PR #46 remains excluded. The schedule stays active because the pause condition requires a clear PR list. No release commands were run. The app dependency install reported the existing 23 audit findings; no dependencies were changed.

  12. johnnyhuy commented on Nov 14, 2026

    @johnnyhuy
    ContributorAuthor

    Reverified origin/main at 93c2a420c5c1e63f687e64f1cf0681b14b7dfaf2 on 14 November 2026. No user-facing change, commit or new PR was needed. #16 and #17 are closed; this issue stays parked with needs-live-provider-verification for Johnny or a reviewer with cloud accounts.

    Both repository gates passed with exit 0.

    • mise run ci:app passed catalog freshness, typecheck, lint, all unit suites and main/preload/renderer builds.
    • mise run ci:cli passed typecheck, all 25 tests with 0 failures and the Linux x64 compiled binary build.
    • git diff --check passed; the worktree is clean.

    Representative proof from mocked responses only:

      ✓ aws mocked 200 returns ok
      ✓ aws Authorization uses SigV4 credential scope
      ✓ aws mocked 403 returns invalid
      ✓ gcp missing config makes no HTTP request
      ✓ gcp mocked 200 returns ok
      ✓ gcp request path carries project and region
      ✓ azure mocked 200 returns ok
      ✓ azure request sends the api-key header
    all cloud probe cases passed
    all probe context cases passed
    all discovery cache cases passed
    ✓ built in 845ms
    
     25 pass
     0 fail
     105 expect() calls
    Ran 25 tests across 2 files.
    compile /tmp/hoist-test bun-linux-x64-v1.3.14
    

    No real credentials or live provider calls were used. Existing credential-source limitations remain as recorded in #48 and #52. Live acceptance checks still need a reviewer with working accounts.

    Sweep completed with 0 merged PRs, 0 closed PRs and 1 stale local agent branch deleted after confirming it was an ancestor of origin/main. Release PR #46 remains excluded. The schedule stays active because the pause condition requires a clear PR list. No release commands were run.

  13. johnnyhuy commented on Nov 14, 2026

    @johnnyhuy
    ContributorAuthor

    Reverified origin/main at 93c2a42 on 14 November 2026. Both repository gates passed with exit 0.

    • mise run ci:app passed catalog freshness, typecheck, lint, all unit suites and the app builds.
    • mise run ci:cli passed typecheck, 25 tests with 0 failures, and the Linux x64 compiled binary build.
    • git diff --check passed; the worktree is clean.

    Mocked-response proof includes aws mocked 200 returns ok, aws Authorization uses SigV4 credential scope, aws mocked 403 returns invalid, gcp missing config makes no HTTP request, gcp mocked 200 returns ok, gcp request path carries project and region, azure mocked 200 returns ok, and azure request sends the api-key header. All cloud probe, probe context and discovery cache suites passed. No real credentials or live provider calls were used.

    No user-facing change, commit or new PR was needed. This issue stays parked with needs-live-provider-verification for Johnny or a reviewer with working cloud accounts. Existing credential-source limitations remain as recorded in #48 and #52.

    Sweep completed with 0 merged PRs, 0 closed PRs and 0 remote branches deleted. Removed the temporary local agent branch created during setup. Release PR #46 remains excluded. The schedule stays active because the pause condition requires a clear PR list. No release commands were run. The app install reported the existing 23 dependency audit findings; no dependencies were changed.

  14. johnnyhuy commented on Nov 14, 2026

    @johnnyhuy
    ContributorAuthor

    Reverified origin/main at 93c2a420c5c1e63f687e64f1cf0681b14b7dfaf2 on 14 November 2026. No user-facing change, commit or new PR was needed. #16 and #17 are closed; #15 remains parked with needs-live-provider-verification.

    Both repository gates passed with exit 0.

    • mise run ci:app passed catalog freshness, typecheck, lint, all unit suites and main/preload/renderer builds.
    • mise run ci:cli passed typecheck, all 25 tests and the Linux x64 compiled binary build.
    • git diff --check passed; the worktree stayed clean.

    Representative proof from this run, using mocked HTTP fixtures only:

      ✓ aws mocked 200 returns ok
      ✓ aws Authorization uses SigV4 credential scope
      ✓ aws mocked 403 returns invalid
      ✓ gcp missing config makes no HTTP request
      ✓ gcp mocked 200 returns ok
      ✓ gcp request path carries project and region
      ✓ azure mocked 200 returns ok
      ✓ azure request sends the api-key header
    all cloud probe cases passed
    all probe context cases passed
    all discovery cache cases passed
    ✓ built in 1.32s
    
     25 pass
     0 fail
     105 expect() calls
    Ran 25 tests across 2 files.
    compile /tmp/hoist-test bun-linux-x64-v1.3.14
    

    No live provider calls or real credentials were used. Johnny or a reviewer with working cloud accounts still needs to perform live acceptance checks. The credential-source limitations recorded in #48 and #52 remain.

    Sweep completed with 0 merged PRs, 0 closed PRs and 0 branches deleted. Release PR #46 remains excluded. The schedule stays active because the pause condition requires a clear PR list. No release commands were run. The app dependency install reported the existing 23 audit findings; no dependencies were changed.

  15. johnnyhuy commented on Nov 14, 2026

    @johnnyhuy
    ContributorAuthor

    Reverified origin/main at 93c2a420c5c1e63f687e64f1cf0681b14b7dfaf2 on 14 November 2026. No user-facing change, commit or new PR was needed. #16 and #17 are closed. This issue remains parked with needs-live-provider-verification pending Johnny or a reviewer with working cloud accounts.

    Both repository gates passed with exit 0.

    • mise run ci:app passed catalog freshness, typecheck, lint, all unit suites and the main/preload/renderer builds.
    • mise run ci:cli passed typecheck, all 25 tests and the Linux x64 compiled binary build.
    • git diff --check passed and the worktree stayed clean.

    Proof from this run, using mocked HTTP responses only:

      ✓ aws mocked 200 returns ok
      ✓ aws Authorization uses SigV4 credential scope
      ✓ aws mocked 403 returns invalid
      ✓ gcp missing config makes no HTTP request
      ✓ gcp mocked 200 returns ok
      ✓ gcp request path carries project and region
      ✓ azure mocked 200 returns ok
      ✓ azure request sends the api-key header
    all cloud probe cases passed
    all probe context cases passed
    all discovery cache cases passed
    
     25 pass
     0 fail
     105 expect() calls
    Ran 25 tests across 2 files. [2.14s]
     [561ms] compile  /tmp/hoist-test bun-linux-x64-v1.3.14
    

    No real provider credentials or live provider calls were used. The credential-source limits recorded in #48 and #52 remain.

    Sweep completed with 0 merged PRs, 0 closed PRs and 0 deleted branches. Release PR #46 remains excluded from the sweep. The schedule stays active because the exit condition requires a clear PR list. No release commands were run.

  16. johnnyhuy commented on Nov 14, 2026

    @johnnyhuy
    ContributorAuthor

    Reverified origin/main at 93c2a420c5c1e63f687e64f1cf0681b14b7dfaf2 on 15 November 2026. No user-facing change, commit or new PR was needed. #16 and #17 are closed; #15 remains parked with needs-live-provider-verification for Johnny or a reviewer with working cloud accounts.

    Both repository gates passed with exit 0.

    • mise run ci:app passed catalog freshness, typecheck, lint, all unit suites and main/preload/renderer builds.
    • mise run ci:cli passed typecheck, all 25 tests and the Linux x64 compiled binary build.
    • git diff --check passed and the worktree stayed clean.

    Proof from this run, using mocked HTTP responses only:

      ✓ aws mocked 200 returns ok
      ✓ aws Authorization uses SigV4 credential scope
      ✓ aws mocked 403 returns invalid
      ✓ gcp missing config makes no HTTP request
      ✓ gcp mocked 200 returns ok
      ✓ gcp request path carries project and region
      ✓ azure mocked 200 returns ok
      ✓ azure request sends the api-key header
    all cloud probe cases passed
    all probe context cases passed
    all discovery cache cases passed
    ✓ built in 1.00s
    
     25 pass
     0 fail
     105 expect() calls
    Ran 25 tests across 2 files. [1.75s]
     [397ms] compile  /tmp/hoist-test bun-linux-x64-v1.3.14
    

    No real provider credentials or live provider calls were used. The credential-source limits recorded in #48 and #52 remain. Live compatibility is still unverified.

    Sweep completed with 0 merged PRs, 0 closed PRs and 0 deleted branches. Only release PR #46 remains open and was excluded. The schedule stays active because the exit condition requires a clear PR list. No release commands were run. The dependency install reported the existing 23 audit findings; no dependency versions were changed.

  17. johnnyhuy commented on Nov 14, 2026

    @johnnyhuy
    ContributorAuthor

    Reverified origin/main at 93c2a420c5c1e63f687e64f1cf0681b14b7dfaf2 on 15 November 2026. No user-facing change or new PR was needed.

    • mise run ci:app passed with exit 0, including all unit suites and the app builds.
    • mise run ci:cli passed with exit 0, including 25 tests, 0 failures and the Linux x64 binary build.
    • git diff --check passed and the worktree is clean.

    Mocked HTTP proof included aws mocked 200 returns ok, aws Authorization uses SigV4 credential scope, gcp missing config makes no HTTP request, gcp request path carries project and region, and azure request sends the api-key header. No real credentials or live provider calls were used.

    This issue remains parked for a reviewer with cloud accounts. Sweep completed with 0 merged, 0 closed and 0 branches deleted. Only excluded release PR #46 remains open, so the schedule pause condition is not met. No release commands were run.

  18. johnnyhuy commented on Nov 15, 2026

    @johnnyhuy
    ContributorAuthor

    Reverified origin/main at 93c2a420c5c1e63f687e64f1cf0681b14b7dfaf2 on 15 November 2026. No user-facing change, commit or new PR was needed. #16 and #17 are closed; this issue remains parked with needs-live-provider-verification for Johnny or a reviewer with working cloud accounts.

    • mise run ci:app passed with exit 0, including catalog freshness, typecheck, lint, all unit suites and the main/preload/renderer builds.
    • mise run ci:cli passed with exit 0, including typecheck, 25 tests with 0 failures, and the Linux x64 compiled binary build.
    • git diff --check passed; the worktree is clean.

    Proof from mocked HTTP fixtures only:

      ✓ aws mocked 200 returns ok
      ✓ aws Authorization uses SigV4 credential scope
      ✓ aws mocked 403 returns invalid
      ✓ gcp missing config makes no HTTP request
      ✓ gcp mocked 200 returns ok
      ✓ gcp request path carries project and region
      ✓ azure mocked 200 returns ok
      ✓ azure request sends the api-key header
    all cloud probe cases passed
    all probe context cases passed
    all discovery cache cases passed
    ✓ built in 894ms
    
     25 pass
     0 fail
     105 expect() calls
    Ran 25 tests across 2 files. [2.26s]
     [447ms] compile  /tmp/hoist-test bun-linux-x64-v1.3.14
    

    No real credentials or live provider calls were used. Live compatibility remains unverified. The credential-source limits recorded in #48 and #52 remain.

    Sweep completed with 0 merged PRs, 0 closed PRs and 0 deleted branches. Only excluded release PR #46 remains open, so the schedule pause condition is not met. No release commands were run. The dependency install reported the existing 23 audit findings; no dependency versions were changed.

  19. johnnyhuy commented on Nov 15, 2026

    @johnnyhuy
    ContributorAuthor

    Reverified origin/main at 93c2a420c5c1e63f687e64f1cf0681b14b7dfaf2 on 15 November 2026. No user-facing change or new PR was needed.

    • mise run ci:app passed with exit 0, including catalog freshness, typecheck, lint, all unit suites and the main/preload/renderer builds.
    • mise run ci:cli passed with exit 0, including 25 tests, 0 failures and the Linux x64 binary build.
    • git diff --check passed and the worktree is clean.

    Mocked HTTP proof included aws mocked 200 returns ok, aws Authorization uses SigV4 credential scope, gcp missing config makes no HTTP request, gcp request path carries project and region and azure request sends the api-key header. No live provider calls or real credentials were used. Live compatibility still needs a reviewer with working cloud accounts; this issue remains parked with needs-live-provider-verification.

    Sweep completed with 0 merged, 0 closed and 0 branches deleted. Only excluded release PR #46 remains open, so the schedule pause condition is unmet. No release commands were run. The dependency install reported the existing 23 audit findings; no dependencies were changed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs-live-provider-verificationParked pending human verification with real cloud provider credentials

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions