Team workbench: local knowledge, policy packs, and route evidence

[Hmbown]

Problem

For teams, CodeWhale needs more than single-user agent power. It needs reproducible local knowledge, project policy, and evidence about model routes, tool use, approvals, cost, and verification. This is the durable foundation for replacing closed hosted assistant workflows with an inspectable open workbench.

Scope

For v0.8.48, define and start implementing team-level workbench primitives.

• Local/private knowledge over repo docs, AGENTS instructions, skills, release runbooks, and project memory.
• Project policy packs for architecture, security, testing, release, docs, and tool approvals.
• Route evidence for each turn: model, provider, thinking level, cost/cache signals, context pressure, tool policy, and verification status.
• CI/PR analysis as structured review tasks with findings-first output and exact source links.
• Export rules that redact secrets and require explicit user action before data leaves the machine.
• Optional hosted/RAG integrations only when deliberately configured.

Acceptance criteria

• A repo can define review/test/release policies in files that are visible to contributors.
• A turn or PR review can show what model/provider/route/tool policy produced the result.
• Local knowledge works without uploading repository content to a hosted index.
• Exports include provenance and redaction status.

Related tracker: #1882
Related presence/help issue: #1890
Related Model Lab issue: #1977