Recapture uncommitted work from stashes, worktrees, and untracked files

[hbmartin]

Recaptures work that existed only in a stash, in untracked working-tree files, and in temporary worktrees — referenced by no branch and one git clean away from being gone.

Audit result

An audit of all 19 local branches and 4 worktrees found the raw dev..branch counts (up to 390 commits) to be almost entirely an artifact of the 2026-08-19/20 upstream rebase. Every commit that looked stranded turned out to already be on dev:

Commit	Claimed missing	Actually
d82b659f2	PR maximhq#6375 pre-auth hook	on dev as 10901184f; 21/23 files identical, the 2 docs files are richer on dev
724052d70	runtime ownership repair	cherry-picking it resolves to a tree byte-identical to dev
556373845	one-click templates	21/25 files byte-identical, other 4 are dev-ahead
0e689788d	harness session ids	on dev as 2a64316c4

So nothing needed cherry-picking. Everything below was uncommitted.

What this PR adds

docs(deploy) — restores the Render/Railway one-click buttons and the ## Hosted one-click choices comparison section from stash@{0}. Buttons and blueprint-verification.json now name dev: the recaptured markup pointed at tree/main, but this fork's origin has no main branch, so that button could never have resolved.

docs — vectorstore-test-infra.md (198 lines), untracked in the working tree. Records why framework/vectorstore tests fail rather than skip without their databases, and that make test-all stops at the first failing target so a red run there is truncated rather than conclusive.

test(transports) — PR maximhq#6333 session-resolution review probes, untracked in a temp worktree. Both packages pass.

One of those tests was rewritten. As recaptured, TestReviewOversizedExplicitSessionIsAccepted asserted an oversized x-bf-session-id passes through verbatim — and it fails on dev, because the merged form of maximhq#6333 caps every ingestion path at schemas.MaxSessionIDLength (session IDs become KV keys and exported trace attributes that nothing downstream bounds). It now guards the behavior that shipped, with the original expectation recorded in a comment.

⚠️ This reverts a deliberate release gate — read before merging

validate-deployment-templates.py fails on this branch:

render.mdx publishes the Render sqlite one-click button while blueprint-verification.json records no verification

That is the gate from #19–#21 working as designed. Every button's last_verified / verified_release is still null, and nothing here fabricates that evidence — the fields are untouched. The validator stops at the first error, so expect the same for the Render postgres and Railway buttons.

Fill those records from a real verified deploy before merging, or drop the docs(deploy) commit. The other two commits are independent of it.

Not included

The 1.6.x working tree held a genuine v1.6.12 backport (su-exec, BIFROST_CONFIG, privilege-drop tests, version bump) that cannot apply to a dev base without reverting the newer entrypoint. It is committed separately as 651100815 on codex/render-railway-1.6.x.

🤖 Generated with Claude Code

---

Summary by cubic

Recaptures uncommitted docs and tests, restores one‑click deploy buttons, and codifies session ID limits in new review tests. The previous review probe expected oversized x-bf-session-id to pass; the new test asserts rejection to match shipped behavior and avoid unbounded keys and attributes.

• Restore Render/Railway one‑click buttons and “Hosted one‑click choices”; bind Render buttons and deploy/render/blueprint-verification.json to dev and render-sqlite.
• Add transports/bifrost-http review tests and benchmarks: parse underscore header form, ensure websocket context drops harness session, and enforce schemas.MaxSessionIDLength (oversized explicit IDs are dropped with no harness fallback).
• Add vectorstore-test-infra.md describing required services, known TLS Redis gaps, and that make test-all stops at the first failing target.
• Required before merge: validate-deployment-templates.py currently fails because verification fields are null. Verify the live templates and populate last_verified/verified_release, or drop the docs(deploy) commit.

^{Written for commit c7aa3f6. Summary will update on new commits.}

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your current included review allowance is based on your included PR review attempts over the past 7 days.

Next review available in: 32 minutes

Limit details: You’ve used the included review currently available. Your 60 included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: f9a8349b-ef66-4b7d-92fc-00c0765ed7ec

📥 Commits

Reviewing files that changed from the base of the PR and between b48db1e and c7aa3f6.

📒 Files selected for processing (7)

• deploy/render/blueprint-verification.json
• docs/deployment-guides/overview.mdx
• docs/deployment-guides/platforms/railway.mdx
• docs/deployment-guides/platforms/render.mdx
• transports/bifrost-http/handlers/session_resolution_review_test.go
• transports/bifrost-http/lib/session_resolution_review_test.go
• vectorstore-test-infra.md

---

_{Comment @coderabbitai help to get the list of available commands.}