KB-10E2

O8C real-DB rollback-only proof readiness (Contabo) — 02-version-milestone-survey

4 min read Revision 1
dieu44iu-cutterv0.6o8creal-db-rollback-proofmilestone-ratifylive-execution-wiringcontabo

O8C Report 02 — Version / milestone survey (G1)

  • macro: v0.6-o8c-real-db-rollback-proof-readiness
  • date_utc: 2026-05-21 · host: vmi3080463 (Contabo)
  • gate covered: G1 deployed runtime + version/milestone survey
  • result: G1 PASS — mismatch classified: patchable-on-Mac (source patch required)

1. Deployed runtime identifiers

cutter_agent/orchestrator/__init__.py in the deployed (O8B 703559c) tree:

__version__          = "0.6.0-O4-live-dryrun-orchestration"
__milestone__        = "O4"      # last ratified code milestone
__execution_enabled__ = False
__live_wiring__      = "O8A-authoring-staging"   # additive O8A marker

2. The mismatch

The deployed tree is the O8B-reconciled O8A live-execution wiring, yet the milestone constants still read O4. This is deliberate and documented: the O8A authoring macro left __milestone__/__version__ at O4 (the milestone-gated test suite pins them) and recorded the wiring via the additive __live_wiring__ marker instead. The O8B-retry final report §8 explicitly recommends an O8C milestone ratify to bump them.

3. Classification — REPORT-ONLY vs MAC SOURCE PATCH

Decision: requires a Mac SSOT source patch. It CANNOT be report-only, and it MUST NOT be patched on the VPS.

Reasons:

  1. __version__ / __milestone__ are source constants in cutter_agent/orchestrator/__init__.py — not runtime config.

  2. The milestone-gated test suite hard-pins them — bumping the constant alone breaks 3 assertions:

    Test Assertion Effect of bump past O4
    test_orchestrator_o4_live_dryrun.py:177 assertEqual(__milestone__, "O4") FAILS
    test_orchestrator_o1_state_machine.py:22 assertIn(__milestone__, {"O1".."O6"}) FAILS for O7/O8x
    test_orchestrator_o2_e2e.py:30 assertIn(__milestone__, {"O2","O3","O4"}) FAILS
    test_orchestrator_o1_state_machine.py:30 __version__.startswith("0.6.0") OK if version keeps 0.6.0 prefix
  3. A milestone bump is therefore a coordinated multi-file source change (1 constant file + 3 test files) that must be committed, tested 394/394, packaged and redeployed — i.e. the host-routing rule required_for_repo_commit_or_artifact_creation: MacBook_dev_host.

  4. VPS is not the SSOT; the macro forbids patching source on the VPS as if it were. No source patch was made on the VPS.

4. Outcome

milestone_mismatch:        deployed wiring is O8A/O8B; constants read O4
classification:            PATCHABLE-ON-MAC (Mac source patch required)
report_only_possible:      NO — source constants + 3 test pins
vps_source_patched:        NO (forbidden; not done)
action:                    Mac command package — see Report 07 §A
recommended_values:        __milestone__   = "O8B"
                           __version__     = "0.6.0-O8B-live-execution-wiring"
                           __live_wiring__ = "O8B-deployed-703559c"  (or drop)
                           + relax the 3 test pins to be milestone-agnostic
g1:                        PASS
Back to Knowledge Hub knowledge/dev/laws/dieu44-trien-khai/v0.6-o8c-real-db-rollback-proof-readiness/02-version-milestone-survey.md