Repository navigation
chore!: complete the Pitot-only runtime cutover - #469
Merged
Merged
Conversation
vishr
enabled auto-merge
November 12, 2026 15:20
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Nov 12, 2026
Read the schema cache under the inflight lock so a stale miss cannot start a duplicate fetch after completion. Treat zombie managers as still stopping until ps reports their disappearance; retain ownership records and avoid signaling unrelated PIDs. The existing completion stress test and a deterministic OS-boundary teardown regression cover both failures caught by the merge queue.
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
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
Pitot's runtime now accepts only the current query contracts. Fresh Pitot media replaces the renamed URLs that pointed at an unprovisioned bucket.
Coordinate cold-cache schema lookup with in-flight fetch retirement to prevent duplicate fetches. The browser harness now waits for zombie managers to be reaped before deleting ownership metadata; a deterministic OS-boundary regression covers that state transition.
Remove the obsolete route registrations, authorization classification, MCP middleware and error-reader conversions; regenerate the embedded browser assets. The previous API paths return 404 and the previous MCP resource is unavailable. Permanent website/documentation redirects remain so existing web links keep working.
Record all four clips from an isolated synthetic telemetry instance using real agent/tool runs. Update the recording assertion to the current empty-state copy and request the four evidence views the recording contract requires. No application API response was intercepted, and no private telemetry was used. Replace the four posters and publish content-addressed clips to the canonical public bucket; no temporary poster-only workaround is included.
Evidence
After: regression tests prove retired API/MCP requests fail and the current reference still works. The canonical bucket/domain is provisioned, and all four new recordings passed the existing populated-view, dashboard, settling and scroll/dwell gates.
just checkpassed, including Go/UI tests, lint, dependency audit, generated assets/docs, release tests and the site validators. The final media site build and 14 recording/timeline tests passed. All four posters were visually reviewed.just test-racerun passed every package exceptTestHigherGenerationMergeYieldsWithoutBlockingDebtRetirementin storage under concurrent load. Its isolated race-enabled rerun passed; this is not reported as a clean aggregate race run.git diff --checkpassed. Public media checks verify HTTP 200, MIME type, immutable caching and byte lengths against the local encoded assets.fanout.runtopitot.devand the published query-reference documentation redirects. No host deployment or backup was performed by this change.Merge Danger
Door: one-way for retired client contracts
Update query API paths, MCP resource requests and error handling before upgrading. This change adds no storage format or control schema migration. Existing persisted storage contracts and published migration bytes are unchanged.
Blast Radius: public