Prepare Oompa 0.8.3 with optional support invitations - #217
Merged
Merged
Conversation
Add shared agent-first CLI discovery after useful results, explicit support commands, native menu actions, and the shared website footer. Preserve stable stdout, programmatic silence, provider preferences, registry-only runtime dependencies, and all daemon/hosted activation gates. Co-Authored-By: Codex <noreply@openai.com>
Preserve private-scope rejection, including suffixed lookalikes. Co-Authored-By: Codex <noreply@openai.com>
Co-Authored-By: Codex <noreply@openai.com>
0thernet
marked this pull request as ready for review
September 16, 2026 06:36
0thernet
added a commit
that referenced
this pull request
Sep 16, 2026
…4 candidate (#221) ## Summary Fixes #220 and prepares the v0.8.4 candidate in one change, modeled on the 0.8.3 preparation in #217. **Migration repair.** Upgrading an HRA 0.5.0 state root (schema 33) to schema 60 failed in the schema-41 provider-usage step with `CODEX_USAGE_UPLOAD_AUTHORITY_INVALID`. Pre-authority releases prune `usage_snapshots` by age and count while retaining up to 128 `usage_cloud_upload_anchors`, so an authentic state root can hold anchors whose snapshots are gone; the backfill derives snapshot authority only from retained snapshots, and the integrity scan refused the whole migration. `retireMigratedUploadAnchorsWithoutSnapshots` now retires such anchors through the existing schema-41 prune trigger before orphan retirement and the integrity scan. Anchors whose snapshot survived are untouched. `oompa daemon start` includes the refused invariant code in its migration failure message. Immutable historical DDL and the migration ledger are unchanged. **0.8.4 candidate preparation.** Package version and description, installer pins and the v0.8.4 public runtime digest, README, release notes, release record, security table, third-party notices, changelog, website content and their contracts move to candidate wording. v0.8.3 remains the admitted canonical GitHub artifact and exact-byte npm release. The candidate needs its own exact immutable artifact admission; daemon startup and hosted command writers stay behind the capacity gate. The reviewed package inventory digest follows the packed-file changes. ## Validation - `bun test ./src/storage --isolate --max-concurrency=1`: 2538 pass, 0 fail, including the new regression for a canonical40 upload anchor whose snapshot was pruned. - Release, package, installer, and site suites after the rebase: 122 pass and 187 pass (site), 0 fail. - `bun run check:install-pins`, `check-install-pins.ts --release-tag v0.8.4`, `check:support-runtime`, `build:site -- --check`, lint on changed files, `bun run typecheck`: clean. - Real-state verification: a copy of the affected HRA 0.5.0 state root opens under this branch and reaches `user_version=60` with the surviving anchor and all seven snapshots retained; the same copy refuses on the previous main with `CODEX_USAGE_UPLOAD_AUTHORITY_INVALID`. - `bun run check:package` passed in a clean single-branch clone with the updated inventory digest; the full local checkout fails that gate only on the pre-existing `rev-list --all` history scan of an unrelated remote branch. Not run locally: the full `bun run check` aggregate and the app build, which trips a staged-file change-time custody assertion in this Documents checkout but passes in a clean clone; relying on Required CI for both. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: 0thernet <894119+0thernet@users.noreply.github.com> Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Prepare Oompa 0.8.3 with optional product updates and development support across the standalone CLI, native menu and shared website footer. Successful useful CLI results expose compact agent discovery on stderr; explicit
oompa supportcommands provide the shared closeout protocol. Task stdout, SDK silence, explicit preferences and existing capacity/daemon/hosted activation gates remain intact.The CLI bundles the reviewed support foundation separately so the public runtime retains its exact registry-only dependency boundary. The bundle is checked against the full source pin, vendor hashes and license; installer digests and the measured 222-entry package inventory are updated for this candidate. Existing published versions remain unchanged.
Validation
Coordination
This branch owns the optional support integration and 0.8.3 candidate. Existing native-foundations PR #209 and its independent runtime/release changes are preserved; no edits are made to that branch.