# Owner-relayed Jarvis stall: credential scope and evidence handoff

Date: 2026-09-06. Recorded by darkwing.
Status: owner-relayed incident account, not independently verified. No investigation
or remediation in the separate deployment is requested or authorized by this note.

## Report preserved

Jason relayed Jarvis's account of three causes:
1. code-be-01 lacked read:package. Repository access did not update the existing
   token's scopes, and registry token exchange returned 401.
2. After re-minting the credential, code-be-01 generated evidence inside the
   infrastructure worktree rather than its agent work/ directory.
3. Jarvis's watch monitored only the agent work/ directory and missed the completed
   evidence. The monitoring mismatch extended the delay.

Reported state at handoff: full digest evidence exists; all three manifests are
pinned in the development infrastructure worktree; the delta remains uncommitted
and unreviewed. Jarvis reports the next gate as validation, commit and independent
review. This is context for that other assignment, not a task or commit/review
authorization for this session.

## Later design and acceptance questions

- Distinguish repository permission, package-registry permission and the scopes
  actually held by an already issued credential. Permission changes must not be
  assumed to update existing tokens. Use explicit capability checks without
  revealing secrets or reflexively widening grants. A 401 alone is not a universal
  diagnosis of this specific cause; the above cause is the relayed account.
- Before dispatch, bind evidence publication to an explicit, authorized artifact
  location and completion contract. Do not infer the path from agent identity or cwd.
- Producers should return a structured receipt containing assignment/run identity,
  canonical artifact locator, digest and completion state. Artifact presence alone
  does not mean validation, commit, independent review or owner acceptance occurred.
- Watchers should bind to the same agreed receipt/location, not maintain a separate
  path assumption. A location change needs an explicit authorized handoff update;
  do not compensate by blindly scanning other workspaces or broadening visibility.
- Distinguish producer failure from observer failure. A missing watched file may
  mean wrong scope/location, delivery failure or monitoring error—not stalled work.
  Reconcile declared publication evidence before retrying or retasking the producer.
- Persist the receipt, watch binding and remaining gates so observer/orchestrator
  restarts can recover the obligation without relying on memory.

Suggested later tests: stale token scopes after an access change; package versus
repository capability refusal; publication at an unexpected location; authorized
location-change handoff; missed/duplicate completion events; watcher restart; and
artifact-present but validation/review still incomplete. Keep all tests synthetic
or separately authorized; never use credential contents as evidence.

Related: foundation mechanical-workflow topics and durability observations dated
2026-09-06. No existing inspector requirement is changed, no worker is retasked,
and no credential, watch, repository or live-fleet operation follows from this note.