Status, measured numbers and limits
State as recorded on 2026-11-16 (session dossier docs/sessions/2026-11-16-codecrucible-build/): CodeCrucible is
built on main from the pure library up to the REST routes, both workflows, the exec worker, the quality image and the
verify steps, all tested locally. Nothing is deployed or enabled. QUALITY_ENABLED is unset everywhere, so the code
ships dormant. Everything left is owner-gated.
Built versus not built
| Area | Bead | State |
|---|---|---|
quality-core: discovery, complexity | CC-1.1 | Built |
| Coverage reader, CRAP | CC-1.2 (.96 real v8 report) | Built |
| Report schema, join, stable ids, aggregate | CC-1.3 | Built |
Gate evaluator, QualityPolicy | CC-1.4 (.98) | Built |
| Static checks, 16 AC9 fixtures | CC-1.5 (.99) | Built |
Quality image, analyze.mjs, run.mjs | CC-2.1 (.100) | Built; image built locally only |
| Out-file support, golden argv | CC-2.2 (.101) | Built |
| Schema, store, migration 0006 | CC-2.3 (.102) | Built; migration not run anywhere |
| Exec worker and activities | CC-2.4 (.103) | Built; never run against a real Temporal server or from the quality-exec Docker target |
qualityAssessmentWorkflow, core activities | CC-2.5 (.104) | Built; tested with fake activities and the Temporal test environment |
| REST routes and config | CC-2.6 (.105) | Built |
qualityVerifyWorkflow steps 1 to 4, 8, 9, intent | CC-3.1 (.106) | Built |
| Solo check, re-kill, controls, AC10 fixtures | CC-3.2 (.107) | Built |
| Pending-submission cap, migration 0007 | .111 | Built |
| Real Temporal starter in the API | .112 | Built |
| Deploy runbook | CC-4.1 (.108, part) | Written (docs/deploy-quality.md) |
| Secrets manifest entries, change requests, baseline run, hand-made verify | CC-4.1 (.108, rest) | Not built (needs the host decision) |
CI enforcement: submit step, scheduled quality-verify status job | CC-4.2 (.109) | Not built |
| Verify activities registered in the exec entry point | none | Not built: quality-exec-main.ts registers only prepareWorkspace, analyze, runChunk, cleanup |
Alerts (global daily limit at 80 percent, any control failure) through ALERT_WEBHOOK_URL | plan section 3 | Not built (runbook: "UNVERIFIED: not wired yet") |
review finding for a 30 percent fall in trusted mutants | plan 4.4 | Not built |
| Line-range chunks (split of one file) | plan section 3 | Not built: one chunk per file |
| Factory loop, exclusions, MCP facade, fast level, continue-as-new beyond 20 chunks | plan section 10 | Later, not planned for v1 |
About 95 files and 21,000 lines were added across these beads (SUMMARY). CI for the last commits was queued or failed on load-related timeouts of the shared runner at wrap time, so local verification is the evidence, not CI.
Preconditions (owner decisions)
| Id | Needed for | State |
|---|---|---|
| PRE-0 Temporal access: an authorizer with a claim mapper, a dedicated cluster, or a written sign-off. A separate namespace does not stop one client from touching others on the shared cluster | Any exec worker on the tailnet | Open; deferred 2026-11-16 until a host exists |
PRE-1 Sandbox host: Linux, Docker, runsc verified, tailnet grant to Temporal only | Spike S3, any non-local exec host | Open |
| PRE-2 Postgres volume on the core host | Phase 4 | Done on the current core host (bead .91, 2026-11-16) |
| PRE-3 Read-only GitHub App key | Any repository fetched from GitHub | Open |
Until PRE-0 and PRE-1 are settled only local development is supported: a Temporal dev server, QUALITY_RUNTIME=runc,
QUALITY_ALLOW_RUNC=own-repo-only, a local mirror.
The rollout order is in deploy runbooks and docs/deploy-quality.md.
Measured numbers
Spikes (Phase 0, docs/p2-findings.md)
Laptop (Apple M3 Pro, 12 cores, 36 GB), Node 24.21.0, Stryker core and vitest-runner 10.1.1, Vitest 5.1.0, TypeScript 6.0.3 (type checks disabled). Host measurements, not the sandbox argv.
| Spike | Measurement | Result |
|---|---|---|
| S1 (hard gate) | src/budget.ts per-file run | 96 mutants, dry run 5 s for 77 tests, total 55 s; 82 killed, 12 survived, 2 no coverage; killedBy on 82 of 82 |
| S1 | trusted list run (host-only config, one empty test) | same 96 tuples in 6 s, set equality with the real run |
| S1 | whole-package list run | 8 files, 417 mutants, 22 s; Stryker ids differ between package and one-file runs, tuples agree |
| S1 | materialized re-kill | killing test alone exit 1; unmutated 0; comment control 0; code control 0 |
| S2 | full packages/agent-core, concurrency 2 | 417 mutants, dry run 5 s, full run 4 min 59 s; 327 killed, 68 survived, 10 no coverage, 3 timeout, 9 runtime error; score 79.1 percent; about 0.7 s wall time per mutant |
| S4 | stability | 20 of 20 unmutated runs passed; 3 full runs: 0 of 417 mutants changed status; scores 79.1, 79.1, 79.1 |
| S5 | offline image prototype | 2.06 GB, cold build 1 min 54 s, 77 of 77 tests under --network none |
| S3 | runsc on a sandbox host | Not run (needs PRE-1) |
Built code (OrbStack, runc, machine under heavy load)
| Check | Result |
|---|---|
| Quality image | 1.79 GB; build 70 to 276 s |
| Analysis | 35 to 92 s; 417 trusted mutants in 8 chunks |
One chunk (src/budget.ts) | 62 to 114 s; 96 mutants: 82 killed, 12 survived, 2 no coverage; 100 percent of tuples join the trusted list |
Exec activities end to end (scripts/quality-exec.test.sh) | 122 s; cleanup idempotent; nothing left behind |
Verify steps 5 to 7 (scripts/quality-verify.test.sh) | 195 s; solo 3 of 3; re-kill confirmed with the new test, not_reproduced with the base tests; controls pass |
| Workflow history of 20 chunks | 147 events (limit 150) |
Not measured: runsc anywhere, a full-package mutation run at concurrency 2 inside the sandbox, a real tailnet exec host,
a real GitHub fetch, and the end-to-end baseline and verify of packages/agent-core (the dogfood).
Stated limits
| Limit | Source |
|---|---|
| Report forgery from test code is mitigated by re-kill and controls, not prevented | runbook |
| Coverage is untrusted and capped by the mutation results | runbook, capCoverage |
| Equivalent mutants are not excluded in v1 | runbook, plan 4.5 |
!(a >= b) control differs from a < b for NaN or undefined operands | quality-core README |
| A retained Stryker timeout with no killers costs credit | FOLLOWUPS |
| A pending submission can leak a slot past its TTL, or when a workflow ends unadmitted (no execution timeout) | ADR 0009, FOLLOWUPS |
readTrees does not heartbeat | FOLLOWUPS |
| Daily limits count a run wholly on its start UTC day | sandboxSecondsToday shortcut |
| Limits are checked at admission and once before the chunks, not per chunk | ADR 0009 |
| Rules 1, 2 and 4 of the static checks are tripwires | quality-core README |
| Cognitive complexity is a SonarSource subset | bead .110 |
| One package per run, at most 20 chunks, one chunk per file | plan, buildAnalysis |
runc is allowed only with QUALITY_ALLOW_RUNC=own-repo-only against a local Temporal dev server (retire at PRE-1, before any other repo, or 30 days after phase 2 starts) | plan risk table |
| Verify is voluntary until CC-4.2 makes it a required status | plan risk table |
Hard numbers at a glance
| Limit | Value |
|---|---|
| Chunks per assessment | 20 |
| Chunk time including dry run | 840 s (policy default 600 s) |
| Analysis container | 540 s |
| Sandbox time per assessment / per verify | 3,600 s / 7,200 s |
| Daily sandbox seconds per client / global | 14,400 / 28,800 |
| Active top-level runs | 1 |
| Pending submissions per client, TTL | 4, 86,400 s |
| Chunk report (gzip) | 128 KiB |
| Analysis out file | 8 MiB raw, 1 MiB gzip |
| Raw out file from a container | 8 MiB |
| Mutants per report | 5,000 |
| Snippet in Postgres | 80 characters |
killed_by in Postgres | 4,096 bytes |
| Findings in Postgres | 64 KiB |
| Credit candidates per verify | 50 |
| Stability and solo runs | 3 and 3 |
| Chunk cache | 2,000 rows, 30-day TTL |
| Survivors page | 200 |
| Workflow history | 150 events, 3 MiB |
| Container | 2 CPUs, 2 GiB, 512 pids, --network none, 1 GiB workspace |
Open items
From docs/sessions/2026-11-16-codecrucible-build/FOLLOWUPS.md and the README:
- Local dogfood (owner decision): hold until 2026-11-17 after 10:00 local, then a baseline and one hand-made verify of
packages/agent-coreend to end (Temporal dev server, core and exec workers withrunc, local mirror, real API), with numbers intodocs/p2-findings.md. - CC-4.1 remainder (
.108), CC-4.2 (.109),.110(cognitive subset; turbo boundary tag forquality-coreundecided). - Re-check CI for the last commits; earlier runs failed on load timeouts.
- Observed while writing these pages (code wins over docs): the verify activities are not registered in
quality-exec-main.ts; the core worker has no separate quality namespace while the API and exec worker can use one;docs/deploy-quality.mdlists aQUALITY_EXEC_TASK_QUEUEvariable thatexec-config.tsdoes not read (the queue is the constantagentforge-quality-exec).
Sources
docs/sessions/2026-11-16-codecrucible-build/README.md,SUMMARY.md,FOLLOWUPS.mddocs/sessions/2026-11-16-codecrucible-build/adr/0009-quality-admission-and-pending-submissions.mddocs/deploy-quality.md(Preconditions, Local evidence, Rollout order, Operations and rollback)docs/p2-findings.md(CodeCrucible Phase 0 spikes; CodeCrucible S5).omc/plans/codecrucible-mutant-hunter.md(sections 3, 6, 7, 9, 10)packages/quality-core/README.mdapps/worker/src/quality-exec-main.ts,apps/worker/src/quality/exec-config.ts,apps/worker/src/worker.tspackages/agent-workflows/src/workflows/quality-shared.ts(QUALITY_RUN_LIMITS),packages/agent-types/src/quality.ts(QUALITY_LIMITS),packages/db/src/quality.ts(sandboxSecondsToday)