Skip to content

feat: add product-owned operational reset - #135

Merged
pcvantol merged 4 commits into
mainfrom
codex/operational-reset-v1
Sep 17, 2026
Merged

pcvantol merged 4 commits into
mainfrom
codex/operational-reset-v1

Conversation

@pcvantol

Copy link
Copy Markdown
Owner

Summary

  • add Forge-owned, schema-aware operational history reset service and forge server reset CLI
  • preserve installation, peer/configuration, security/authority, allocator, anti-replay, and qualification bindings
  • add durable writer fencing, consistent verified backups, resumable artifact handling, dataset generations, and replay tombstones
  • add fixture-only destructive/crash/recovery qualification and operator runbook
  • bump Forge once to 2.7.22 / runtime schema 38
  • fix bounded PyPI release readback filename normalization and registry polling

Safety boundary

No production reset, Mission, credential rotation, orphan cleanup, or historical acceptance mutation was performed. Destructive tests use isolated temporary Forge roots only. Live installation remains blocked pending an authorized product-owned Forge updater route.

Validation

  • bash scripts/validate.sh: 702 tests passed
  • PRODUCT_VERSION=PASS version=2.7.22
  • offline projection validation: PASS
  • reset-focused: 23/23 passed
  • combined reset/runtime: 57/57 passed before release-readback integration; full exact-head gate above passed after integration

@pcvantol
pcvantol merged commit e167ddd into main Sep 17, 2026
5 checks passed
@pcvantol
pcvantol deleted the codex/operational-reset-v1 branch September 17, 2026 17:39
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