Orchestrate provider-aware team knowledge context

[adrianwebb]

Outcome

The control plane compiles and enforces provider-aware assignment context, manages the Team Library, authorizes scoped cross-project retrieval, and publishes current TreeDX knowledge reliably.

Work authority

• Work item / Issue: Closes Orchestrate provider-aware context and managed team knowledge #158
• Proposal / decision: User-approved Provider-Aware Agent Context and Team Knowledge Architecture plan in the active Codex task.
• Assignment / checkpoint: Active Codex task; implementation integration checkpoint.
• Actor: Codex / OpenAI
• Human authority: @adrianwebb
• Agent / capacity provider: Codex desktop task under @adrianwebb authority
• Exact base ref: staging at 1bdbac0
• Exact head ref: codex/provider-aware-context-control-plane at 4be58b3

Contributor mode (select one):

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

Plan

Implement managed Team Library lifecycle, layered context admission, permission-scoped sharing and retrieval, provider capacity enforcement, logical TreeDX reads, and reliable prioritized knowledge publication. Status: implemented and verified after rebasing onto current staging.

Changes and commits

• 4be58b3 — provider-aware context and team knowledge orchestration, including the bounded assignment planner support extraction.

Verification

• I ran the narrowest relevant package verification and documented any checks that could not be run.
• npm test — 75 files, 217 tests passed.
• npm run check:file-lengths — passed; no handwritten file exceeds 500 lines.
• npm run build:dist — passed.

Risk and rollback

Risk is concentrated in context admission, authorization intersections, and asynchronous publication. Tests cover each boundary. Roll back by reverting 4be58b3; additive schemas and services do not require destructive data rollback.

Completion summary

Implementation is complete, rebased on current staging, locally verified, and ready for staging integration. No known blocker remains.

AGPL committer authorization

The authenticated PR author is checked by the repository-owned authorization workflow.

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.