Add a concrete 0-100 swarmness/compliance score, local large-scale stress, and 3000 TPM budget acceptance so the repo can say when it is a swarm by measured criteria instead of prose alone.
Constraint: user required Chinese docs, explicit scenarios, parameters, formulas, pass/fail lines, and git upload.
Rejected: prose-only PASS reports | they did not answer whether the system is a swarm with a concrete score.
Confidence: high
Scope-risk: moderate
Directive: keep production runtime claims separate from local minimal swarm acceptance scores.
Tested: py_compile swarm_minimal examples tests; unittest discover -s tests 45 tests; run_swarm_compliance_score.py; run_tpm_budget_acceptance.py; run_academic_standard_evaluation.py; git diff --check; docs/script secret-pattern scan.
Not-tested: live S07 and production Kubernetes/NewAPI provider-rate-limit stress were not rerun in this upload step.
Co-authored-by: OmX <omx@oh-my-codex.dev>
