Skip to content

fix(cli): keep owner-agent status working after introspection hardening - #144

Merged
tnunamak merged 1 commit into
mainfrom
fix/owner-agent-status-after-auth-hardening
Aug 14, 2026
Merged

fix(cli): keep owner-agent status working after introspection hardening#144
tnunamak merged 1 commit into
mainfrom
fix/owner-agent-status-after-auth-hardening

Conversation

@tnunamak

Copy link
Copy Markdown
Contributor

The authorization stack now protects /introspect for confidential AS↔RS callers. The owner-agent CLI still used the owner bearer at that endpoint, so owner-agent status failed with HTTP 401 in the post-merge reference smoke.

This follow-up keeps the existing introspection path where it works, and falls back on an HTTP 401/403 to the bearer-authenticated /v1/owner/control surface already advertised for owner agents. It reports only non-secret status. The live smoke fixture now registers the Northstar connector, materializes the owner instance, and ingests into that exact instance so it matches the frozen Source-instance read contract.

Validated: CLI build; owner-agent tests 40/40; live owner-agent reference smoke; targeted Ultracite; diff-check.

Assisted-by: AI

Owner-agent status falls back to the bearer-authenticated control surface when AS introspection requires RS credentials. The reference smoke now seeds the owner connector instance used by the frozen Source read contract.

Assisted-by: AI
Signed-off-by: Tim Nunamaker <tnunamak@gmail.com>
@vercel

vercel Bot commented Aug 14, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
pdpp Ready Ready Preview Aug 14, 2026 3:24pm

Request Review

@tnunamak
tnunamak merged commit 465a95a into main Aug 14, 2026
10 checks passed
@tnunamak
tnunamak deleted the fix/owner-agent-status-after-auth-hardening branch August 14, 2026 15:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant