Combat V2 existed as a preserved experiment; the First Night route was a functional gray-box sequence with generic presentation.
← Portfolio overviewpaused
Godot arcade boxing RPG
Cock Fight 2000
The First Night gray-box route gained a coherent Combat V2 handoff, exact result and rollback contracts, and a readable product shell. A distinct whole-frame fighter pass remains candidate work.
Outcome
Two leaves accepted; fighter-art candidate awaits critique
This report separates accepted product truth from preserved candidate work. A missing critic or device proof is treated as an open gate, not a semantic technicality.
Apartment-to-bout-to-result-to-home now works with atomic prep rollback and truthful resource trades. Scarlet and Dockhand art, attack registration, and Backyard Card presentation are preserved but unaccepted.
Accepted boundary
- LEAF-001 Combat V2 handoff, exact result, and cancel/re-entry rollback
- LEAF-002 coherent Apartment → Cal → prep → bout → result → home shell
- Paid Hard Sparring truthfully trades +$12 for -7 condition
- Four deterministic soak signatures and 25 audio cues
Held, candidate, or unstarted
- LEAF-003-R3 whole-frame Scarlet and Dockhand candidate has no fresh critic verdict
- LEAF-004 and final reality gate were never opened
- Gamepad behavior has equivalent coverage but no physical-device acceptance
Gate history
Decision timeline
The useful unit is not the turn. It is the gate: a bounded claim, its evidence, and the verdict that controlled promotion.
Authored F11 whole-frame Combat V2 selected; segmented F10 kept historical.
First Night combat handoff and atomic prep rollback accepted.
Product shell and truthful three-choice prep accepted.
Distinct fighter atlases and corrected jab/hook cells preserved.
Native keyboard automation could not advance; no source, Web, or test verdict was produced.
Candidate remained unaccepted; later leaves stayed closed.
Existing evidence
Frames from the run.
No images were generated for this report. These are existing repository artifacts with shortened SHA-256 anchors. Candidate frames remain visibly labeled.
Testable now
Reproduce the current truth.
Commands are repository-root commands from the project's canonical debrief. They are shown for technical review, not as a public playable deployment claim.
godot --headless --path . --script tests/combat_v2_presentation.gd
godot --headless --path . --script tests/combat_v2.gd
godot --headless --path . --script tests/combat_v2_soak.gd
godot --headless --path . --script tests/combat_v2_first_night_handoff.gd
godot --headless --path . --script tests/first_night_product_shell.gd
godot --headless --path . --script tests/audio_manifest.gdThese checks cover the accepted shell and combat contracts. R3 art is deliberately not represented as an accepted release.
2/36atlas cells changed each
34/36cells preserved each
14deterministic scenarios
25audio cues
Git anchors
- LEAF-001 664a522
- LEAF-002 9b08af9
- R3 candidate 7e0d517
- Wind-down 8d4d2c7
Known token floor
3,519,868
Known project telemetry, including the stopped hidden lead where recorded; descendant totals remain incomplete.
Candid postmortem
Failures that changed the run.
The point of the case study is not that agents wrote code. It is that the system found reasons not to trust its own first answer.
Loops, stalls, and defects
- The first prep flow stacked canceled Food and Nap effects before atomic rollback was added.
- The R3 critic could not advance native input and stopped without reviewing source, Web, or tests.
- A missing verdict was correctly treated as neither PASS nor REVISE.
- Earlier segmented limbs remained historical; the run stayed on the authored whole-frame combat model.
What carries forward
- Tiny atlas surgery can preserve identity: only two of 36 cells changed per fighter.
- A critic that cannot establish control should stop, not improvise a verdict.
- Accepted mechanics and candidate art can coexist without blurring release truth.
Exact next safe action
Start one fresh critic with a proven input route, inspect native and Web behavior plus source and tests, and issue an explicit PASS or REVISE for R3. Only then decide whether to promote the fighter package and open LEAF-004.