Make Team Library repositories team-unique

[adrianwebb]

Outcome

Completes the provider-aware context integration without allowing two teams under one GitHub owner to adopt or delete the same managed Team Library repository, and prepares API rc62.

Work authority

• Work item / Issue: Make managed Team Library repositories team-unique before rc62 #163
• Proposal / decision: N/A — architectural acceptance correction in the active Platform release chain
• Assignment / checkpoint: Verify and release the completed Agent context and communication integration
• Actor: Codex
• Human authority: adrianwebb
• Agent / capacity provider: Codex on dev2
• Exact base ref: staging at 465afa5016bbbfcfa95ff606ada72eeb89104f3c
• Exact head ref: e726c6f0921ed4c6ee6bca9ae3796eb18e34f761

Contributor mode (select one):

• Human-authored
• Agent-assisted under human authority
• Agent-authored under human authority

Plan

Audit the cross-repository context architecture, repair the only ownership collision, verify current staging, publish rc62, and compose it with SDK rc66, Agent rc40, and TreeDX rc13.

Changes and commits

• e726c6f0921ed4c6ee6bca9ae3796eb18e34f761 — deterministic team-unique repository identities, exact recorded-name reconciliation/deletion, legacy compatibility, tests, and rc62 metadata.

Verification

• Fresh npm ci against the updated SDK rc66 lock.

• npm run verify:direct: build passed; 76 files / 222 tests passed.

• Tests prove deterministic uniqueness, legacy compatibility, and rejection of another team's repository identity.

• Platform remains configuration/documentation-only; managed libraries remain API/TreeDX runtime resources and are not source workset entries.

• I ran the narrowest relevant package verification and documented any checks that could not be run.

Risk and rollback

Existing system projects retain the recorded legacy team-library identity. New teams receive team-library-<12 hex> derived from the stable team ID. A mismatched deletion identity fails closed. Revert this commit and retain API rc61 if release gates fail; no database migration is introduced.

Completion summary

The context architecture is compatible with multi-team production and ready for protected staging verification and rc62 publication. Closes #163.

AGPL committer authorization

The provider-authenticated author is the approved account adrianwebb; no identity override or token is included in the workspace.

Submission checklist

• The change is bounded to the stated work item and target repository.
• Exact base and head refs are recorded and the branch is ready for review.
• Verification and compatibility evidence are recorded above.
• No plaintext secrets, credentials, machine state, or unrelated residue are included.
• Plan, status, commits, and completion summary form a complete durable record.
• Rollback or recovery steps are documented and executable.