Build Project Capability Compiler v1

[pate0304]

What

• compile repository evidence into a Project Capability Map, Work Packages, Team IR, and Focused/Recommended/Extended team proposals
• generate project-specific agents from capability coverage while keeping the 111-entry catalog as reusable primitives, not a fixed team size
• add strict lifecycle/ownership lineage, exact freshness checks, trusted Git resolution, preview-safe voice approval, and lock-scoped revalidation
• replace runtime-variable gzip packaging with a deterministic 12-file tar and regenerate the SBOM/checksums
• expand fixture, golden, property, adversarial, migration, transaction, CLI, and lifecycle coverage

Why

Codesemble should recommend the smallest evidence-bound team a project needs. It should not promise or generate a fixed 111-agent team, and it must preserve human approval, least privilege, replay/freshness safeguards, and recoverable writes.

Impact

• v0.2 Project Capability Compiler candidate
• no global Codex configuration changes
• no release or package publication
• physical Android voice validation remains a separately tracked boundary

Validation

• Node 26.5.0: 140/140 tests across 20 files, typecheck, build, catalog validation
• Node 24.13.1: 140/140 tests across 20 files and identical archive digest
• deterministic plugin tar: d93fd8a98237933dbac1a93dcca87ce3733cc7d2ffaadd682b1294656942097b
• logical 12-file plugin payload: 95c65a6f991fc1300d6af0551bf1934d6a7beb153008220aa9cd5f7f69e3a005
• 120 source payload checksums verified
• deterministic CycloneDX SBOM: 128 components verified against the lockfile
• official source/extracted plugin and four skill validators passed
• npm audit: 0 vulnerabilities
• independent architecture, security, and Definition-of-Done reviews passed
• exact v0.2 archive installed into an isolated Codex home and disposable trusted project
• preview no-write, plan-bound voice approval, eight-role apply, fresh generated-role orchestration, bounded capacity refusal, trivial no-spawn, meaningful update, true no-op, and reverse rollback verified
• all three runtime transactions rolled back; tracked test-project bytes preserved and recovery receipts retained
• final-head GitHub Actions passed on Node 22/24 across Ubuntu, macOS, and Windows; dependency review and CodeQL passed
• Codesemble project workspace applied the plan-bound 13-role team as transaction 148b1ccd-3369-4c88-974b-3c6dd340561d; independent Doctor passed all checks
• fresh native root 019fbee8-013f-7800-bf1f-2036c08bfa65 used the master orchestrator and generated verification specialist, then integrated ROOT-OK ORCH-OK TESTCMD=vitest run

Remaining external boundaries

• physical Android microphone and speech-recognition usability remain separately labeled, not claimed by transcript/runtime semantics
• merge, release, signing, marketplace publication, and directory submission remain separately authorized

Closes #7
Closes #8
Closes #9
Closes #10
Closes #11
Closes #12
Closes #13
Closes #14
Closes #15
Closes #16
Closes #17
Closes #18
Closes #19
Closes #20