Skip to content

chore!: complete the Pitot-only runtime cutover - #469

Merged
vishr merged 2 commits into
mainfrom
chore/pitot-only-cutover
Nov 12, 2026
Merged

vishr merged 2 commits into
mainfrom
chore/pitot-only-cutover

Conversation

@vishr

@vishr vishr commented Nov 12, 2026 •

Copy link
Copy Markdown
Member

Summary

Pitot's runtime now accepts only the current query contracts. Fresh Pitot media replaces the renamed URLs that pointed at an unprovisioned bucket.

- previous query API/MCP aliases and error-code translation
+ /api/pitotql/, pitot://pitotql/reference, invalid_pitotql
- media URLs without a hosted destination
+ eight verified immutable clips at assets.pitot.dev

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

  • Before: retired runtime contracts remained accepted, and the media hostname/bucket was absent.
    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 check passed, 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.
  • The full just test-race run passed every package except TestHigherGenerationMergeYieldsWithoutBlockingDebtRetirement in storage under concurrent load. Its isolated race-enabled rerun passed; this is not reported as a clean aggregate race run.
  • The cold-cache completion test reproduced duplicate fetches before the coordination fix and passed 1,000 race-enabled repetitions afterward. The complete PitotQL race suite passed. The new teardown regression fails under the old completion predicate and passes with the reaping check.
  • Actual Chrome playback verified both videos in both themes at 1280×800 from the public canonical URLs.
  • Staged Gitleaks and git diff --check passed. Public media checks verify HTTP 200, MIME type, immutable caching and byte lengths against the local encoded assets.
  • Live checks preserve fanout.run to pitot.dev and 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

@vishr
vishr enabled auto-merge November 12, 2026 15:20
@vishr
vishr added this pull request to the merge queue Nov 12, 2026
@github-merge-queue
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.
@vishr
vishr enabled auto-merge November 12, 2026 15:39
@vishr
vishr added this pull request to the merge queue Nov 12, 2026
Merged via the queue into main with commit 74f2157 Nov 12, 2026
32 checks passed
@vishr
vishr deleted the chore/pitot-only-cutover branch November 12, 2026 15:54
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