keisei/KeiSeiKit-1.0
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix(ci): regenerate insta golden snapshots after Wave A scrub

Browse source 
After session-wide kit scrub (CfC/Born-like/KILL GUARD/etc → generic),
_assembler/tests/snapshots/{code-implementer,researcher}.snap held stale
expectations. CI failed on golden_code_implementer + golden_researcher
across 9 consecutive runs.

Regenerated via cargo-insta accept. Snapshot diffs are exactly the term
substitutions Wave A applied to manifests:
  - "ML/RL/CfC-adjacent" → "ML/RL specialized-node"
  - similar 1-line shifts in code-implementer.snap

cargo test --release now green across all 11 _assembler test binaries
(22+3+3+3+1+2+2+7+4+6 = 53 tests passing).

=== STATUS-TRUTH MARKER ===
shipped: functional
stubs: 0
cargo-check: PASS
cargo-test: PASS (53 tests, 0 failures)
behaviour-verified: yes
follow-up-required:
  - none — CI should turn green on next push

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
Parfii-bot 2026-05-01 18:28:28 +08:00
parent 785ad75aaa
commit 8e39e4186f
2 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
_assembler/tests/snapshots/code-implementer.snap
View file

@ -407,7 +407,7 @@ Blockers / next: <list>
- Skipping the Pre-Dev Gate on non-trivial work
- Fixing immediately after Phase 1 of audit without running Phase 2
- Third attempt with the same failed approach (escalate to Error Budget Level 2 instead)
- Running `modal app stop` / `pkill` on a running paid job without explicit user confirmation (KILL GUARD applies)
- Running `modal app stop` / `pkill` on a running paid job without explicit user confirmation (anti-stop guard applies)
- Rewriting working code without a stated reason (Core Rule 3: Don't Rewrite Working Code)
- Patching a broken formula with overlay logic instead of fixing it at the root (Core Rule 1: No Patching)

4
_assembler/tests/snapshots/researcher.snap
View file

@ -187,7 +187,7 @@ Rules: architectural decision → E1-E2. Financial (compute) → ONLY E1. Data >
**Out (hand off):**
- `validator` — claim needs hard verification (citation sanity, reproduce-in-tests, RULE 0.4 gate before commit)
- `ml-researcher` — question is ML/RL/CfC-adjacent (Math-First + tooling-reuse + synthetic-to-real discipline)
- `ml-researcher` — question is ML/RL specialized-node (Math-First + tooling-reuse + synthetic-to-real discipline)
- `patent-researcher` — question touches patent prior art, FTO, or novelty (IP-aware handling required)
- `architect` — question is structural/architectural — dependency graph, pattern inventory, module boundaries
- `critic` — findings suggest anti-pattern sweep or Constructor-Pattern violation review
@ -195,7 +195,7 @@ Rules: architectural decision → E1-E2. Financial (compute) → ONLY E1. Data >
# HANDOFFS
- **validator** — claim needs hard verification (citation sanity, reproduce-in-tests, RULE 0.4 gate before commit)
- **ml-researcher** — question is ML/RL/CfC-adjacent (Math-First + tooling-reuse + synthetic-to-real discipline)
- **ml-researcher** — question is ML/RL specialized-node (Math-First + tooling-reuse + synthetic-to-real discipline)
- **patent-researcher** — question touches patent prior art, FTO, or novelty (IP-aware handling required)
- **architect** — question is structural/architectural — dependency graph, pattern inventory, module boundaries
- **critic** — findings suggest anti-pattern sweep or Constructor-Pattern violation review