Skip to content

Harden receipt retention, lifecycle composition, and CI gates - #48

Open
brainx wants to merge 5 commits into
mainfrom
work/zeus-hardening
Open

Harden receipt retention, lifecycle composition, and CI gates#48
brainx wants to merge 5 commits into
mainfrom
work/zeus-hardening

Conversation

@brainx

@brainx brainx commented Sep 14, 2026

Copy link
Copy Markdown
Owner

Summary

Receipt admission previously stopped after 10,000 retained records. Add read-only capacity reporting and explicit, bounded archival of terminal receipts while preserving complete request-key replay history. The additive schema-10 migration keeps existing receipt identities and uniqueness rules.

  • Require successful results from all six supported CI dependencies through ci-required, and include that aggregate in release verification.
  • Replace the supervisor's behavioral inheritance chain with one concrete core and stateless operation services, preserving public signatures, callback overrides, locking, and process-ownership behavior.
  • Put local onboarding before audit guidance, correct the Hermes version command, and verify subsystem boundaries and the installed offline workflow.

Test Evidence

Validated source: 70c8178.

  • GitHub CI passed for both the pull-request run and push run: all 20 checks succeeded, including ci-required, real Hermes, Docker isolation, and macOS lifecycle.
  • make check: both unittest runs executed 1,596 tests with 3 skips; source/branch coverage 84.10% versus 83.91% on the unchanged baseline. Repository contracts, formatting, lint, mypy, Bandit, and ShellCheck passed.
  • sh scripts/wheel_smoke.sh: passed on the committed source, including installed fake-Hermes start/status/stop, capacity, and archive preview with real Hermes/Docker commands blocked.
  • twine check dist/* and git diff --check main...HEAD: passed.
  • Storage drill: 25,001 retained receipts, including 11,001 actual prepare/finish admissions and 14,000 seeded historical rows. Separate regressions cover replay, stale writers, clock rollback, transaction failure, and migration rollback.

The bulk drill disables durability only inside its test fixture for speed; production FULL transactions are tested separately. It is not power-loss or physically exhausted-disk evidence.

Risk

  • Schema 10 requires quiesced writers and a complete state/profile backup before upgrade. Older binaries reject the new schema; rollback restores the matching pre-upgrade state and binary. Logical archival frees admission slots, not disk space.
  • Olymp must explicitly support the 0.6.1.dev0 / schema-10 pairing before a coordinated deployment. Its compatibility proposal is separate and is not included or applied here; the development version string alone is insufficient.
  • GitHub required-check enforcement still needs a separate repository-settings rollout. This PR does not change repository protection settings.
  • Local verification skipped real Docker isolation, Linux renameat2, and the pinned Hermes audit-broker integration. One earlier lifecycle startup test returned no PID, then passed in isolation and both final full runs. Failure diagnostics were added without weakening assertions; the intermittent cause remains unestablished.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant