Consolidate runtime and deployment tooling with upgrade compatibility - #963
Open
ReganBell wants to merge 6 commits into
Open
Consolidate runtime and deployment tooling with upgrade compatibility#963ReganBell wants to merge 6 commits into
ReganBell wants to merge 6 commits into
Conversation
Preserve existing public authentication, credential grants, and surface features while adopting durable execution, expanded sandbox backends, and shared deployment tooling. Retain migration checksums and legacy database compatibility, restore recoverable Slack delivery, and document upgrade boundaries.
Declare bounded public plugin routes, reject reserved API paths, and verify routing precedence. Restore fixture consistency and public publishing checks, and keep static analysis aligned with executable entrypoints.
Show restored model cards and a real two-file web turn using synthetic development data.
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
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
2 participants
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.
Merge is held pending deployment qualification of the exact PR commit. Qualification must complete before this change lands on main or is released.
This consolidates the runtime and deployment tooling while preserving existing public authentication, credential grants, sandbox contracts, and web/Slack behavior. It adds durable execution and session-tape recovery, shared deployment tooling, expanded sandbox backends, and configurable plugin routes.
Migration identifiers and checksums remain stable. Startup repairs run before registered migrations, completed legacy webhook sweeps are adopted without re-disabling re-enabled hooks, and legacy cron history remains readable across rolling upgrades. Slack multi-file delivery retains the durable delivery marker used to recover after a lost acknowledgement. AWS role credentials continue to run under the existing grant, policy, isolation, and redaction boundaries.
Upgrade notes are in
docs/upgrading-runtime.md. Sandbox publish/image pins, secondary-backend configuration, and reach-denied notifications are retired. Older binaries do not display newly recorded cron history, which remains durable and visible after rolling forward.Validation includes existing-public and consolidated-schema upgrade/rollback checks, 225 Postgres tests, full CLI and surface suites, targeted authorization/cancellation/delivery regressions, typecheck, lint, and independent reviews covering data compatibility, credentials, delivery recovery, public routing, and disclosure. Live checks exercised a real model reply, persisted transcript and title, two generated file attachments through the web UI with successful content-checked downloads, and restored admin model cards. Final Firefox Slack QA also delivered two generated files together and the final confirmation once.
The screenshots below show a local Acme dev instance using a real model and sandbox, with synthetic QA files. The model connection, attachment flow, and admin cards are live; no API responses are mocked.
All checks pass on the final candidate, including CodeQL and Postgres. PR checks prompted deterministic timing fixtures, safer error formatting, and exact URL assertions. False-positive security findings were independently reviewed against their actual data flows, with the rationale recorded on each alert. Deployment qualification remains the gate before merge.