Work Package Prompt: WP02 – Charter leg + dossier module + measured timings

Objectives & Success Criteria

a src/specify_cli/dossier/** edit routes to dossier without forcing run-all.

bijection, verbatim, two-authority, and measured-timings guards are green.

select_modules(manifest) ⊇ {charter, dossier} for all four manifests (turns WP01 green).
dossier is a real registry module with test_dirs [tests/dossier, tests/specify_cli/dossier];
Registry / scrub / router-filter stay verbatim in lockstep (NFR-001); the claim-once,
.github/ci-shard-timings.json carries a real measured dossier capture (FR-005).

Context & Constraints

traces/design-decisions.md (router verbatim guard forces the glob into scrub/registry roots too; the file-specific glob is harmless — the ci group precedent carries non-src roots).

C-003: no product code. NFR-002: no new size/length ratchet.

Grounding + guard map: research/code-grounding.md. Flagged deviation from the brief recorded in
C-001 router verbatim: ordered-equal across all three authorities. C-002: file-specific glob only.

Branch Strategy

Strategy: {{branch_strategy}}
Planning base branch: {{planning_base_branch}}
Merge target branch: {{merge_target_branch}}

Subtasks & Detailed Guidance

Subtask T003 – Charter leg (commit 1)

charter group roots in tests/release/ci_retirement_scrub.json, the charter row roots in .github/ci-module-registry.yml, and the charter filter group in .github/workflows/ci-router.yml.

Purpose: Make a manifest edit select the charter module.
Steps: Append packs/built-in/missions/**/expected-artifacts.yaml (ordered, last) to the
Files: the three authorities.

Subtask T004 – Dossier scrub group + registry row + out-of-matrix release (commit 2)

roots: ["src/specify_cli/dossier/", "packs/built-in/missions//expected-artifacts.yaml"], cov_targets: ["specify_cli.dossier"], census_evidence: "known-live".

scrub, tier: standard, test_dirs: [tests/dossier, tests/specify_cli/dossier], provisional shard_count: 1); remove tests/dossier and tests/specify_cli/dossier from out_of_matrix_test_dirs.

Steps:
tests/release/ci_retirement_scrub.json: add group dossier,
.github/ci-module-registry.yml: add the dossier row (roots/cov_targets verbatim from

Subtask T005 – Dossier router wiring (commit 2, with T004)

the scrub roots); add the dossier changes.outputs line (same shape as peer src-backed groups); add dossier to the unmatched for-loop; OR needs.changes.outputs.dossier == 'true' into the architectural-heavy if:.

Steps in .github/workflows/ci-router.yml: add the dossier filter group (globs verbatim

Subtask T006 – Measured shard timings (commit 3)

capture); confirm module_test_count[dossier] == len(module_test_durations[dossier]); set the registry shard_count to the measured value so inter-shard skew ≤ 20% (shard_count 1 trivially passes). Commit the timings + the final shard_count.

Steps: python scripts/ci/capture_shard_timings.py --module dossier --write (real serial

Test Strategy

test_gate_selection_authority.py, test_module_shard_registry.py, test_retirement_scrub.py, test_out_of_matrix_evidence.py, test_ci_router_transcription_guards.py, test_ci_quality_path_filters.py, test_ci_corpus_trigger_completeness.py, tests/ci/test_ci_module_wiring.py, the WP01 parity gate, plus tests/dossier + tests/specify_cli/dossier (prove the newly-routed module green).

make test-fast + the specific named gates (NOT a tests/architectural/ sweep):
ruff check + ruff format --check --force-exclude on changed files; mypy-clean new code.

Risks & Mitigations

Verbatim guard list-equality → ordered-append everywhere.
Claim-once guard → remove the two dirs from out_of_matrix_test_dirs in the same commit.
Shard-timings strict check → measured capture; the registry row must exist before capture runs.

Review Guidance

once; the parity gate is green; tests/dossier + tests/specify_cli/dossier pass; the timings are measured (provenance producer == scripts/ci/capture_shard_timings.py).

Verify the three authorities are byte-verbatim for charter and dossier; the dirs are claimed

Progress & Status

Progress/status live in status.events.jsonl (spec-kitty agent tasks ...).

Spec Kitty

Kanban Board