Turn the remaining minimal-boundary items into executable behavior: locked autonomous claim scaling for 3/5/7 agents, multi-candidate fusion, and challenge-revise-revote consensus.
Constraint: The user asked to implement code directly, complete testing and acceptance, and explain the test standards rather than only updating the comparison document.
Rejected: Leaving SW-AQS-16, candidate fusion, and questioning consensus as documentation-only future work | each now has deterministic code paths and S09 acceptance evidence.
Confidence: high
Scope-risk: moderate
Directive: Future claims about full production readiness must still distinguish this local deterministic S09 acceptance from real runtime/Kubernetes scaling and Manager/Agnet platform integration.
Tested: .venv/bin/python -B -m py_compile swarm_minimal/*.py examples/*.py tests/*.py; .venv/bin/python -B -m unittest tests.test_standard_scenarios; .venv/bin/python -B -m unittest discover -s tests; .venv/bin/python -u -B examples/run_next_boundary_acceptance.py; .venv/bin/python -u -B examples/run_academic_standard_evaluation.py; .venv/bin/python -u -B examples/run_standard_scenario_acceptance.py; .venv/bin/python -B examples/export_model_agnet_io_report.py; .venv/bin/python -B -m unittest tests.test_model_io_report_audit; docs secret pattern scan; git diff --check.
Not-tested: Real Kubernetes/worker runtime 3/5/7 scaling, Redis Stream consumer-driven replanning, and Manager/Agnet approval integration remain outside this local minimal acceptance.
Co-authored-by: OmX <omx@oh-my-codex.dev>