Measurement
https://objectstack.ai is serving deployment dpl_2nfWjGjSwZjakVEmUG1kBWD6697r. That id is unchanged across 19 merges to main, four of which touched apps/docs, over roughly two hours.
dpl: dpl_2nfWjGjSwZjakVEmUG1kBWD6697r | age: 6510 | x-vercel-cache: HIT
The live generation can be dated precisely by what it does and does not contain:
| landed on main | live? |
|---|
#12253/robots.txt + /sitemap.xml (16:31) | ✅ serving |
| #12258 dotted-path 404 guard (16:52) | ✅ serving (/foo.txt → 404) |
#12262 one <h1> per page (16:57) | ❌ /docs/data-modeling/objects still renders 2<h1> |
| #12284 homepage title (16:57) | ❌ still ObjectStack — Apps small enough for AI to hold whole. |
#12303X-Robots-Tag on agent-reader copies | ❌ header absent |
#12305metadataBase + canonical | ❌ no canonical on any page type |
| #12325 Open Graph cards | ❌ (merged after the above) |
So production is pinned to a build made between 16:52 and 16:57 on 2026-08-25.
Control: this is not CDN staleness that a request can defeat. Cache-Control: no-cache / Pragma: no-cache request headers and a cache-busting query string both still return x-vercel-cache: HIT with an age of 6510s, and the data-dpl-id embedded in the HTML — which is a property of the build, not of the cache entry — has not moved.
Why it matters
Five merged PRs from epic #12243 are invisible to users and to crawlers, and the epic's definition of done is written against the live site, so it cannot be verified while this holds. Three of its five boxes were ticked against production earlier today; the rest cannot be.
What is needed, and why it is not a PM action
Everything visible from GitHub is green: all five PRs merged through the merge queue with full CI. Whatever is stuck is on the Vercel side — a failing production build, a paused project, a promotion that is not happening — and reading that requires the Vercel dashboard or API token for the docs project. No agent in this repo has it.
Maintainer action: check the docs project's deployment list for a failed or queued production build since ~16:55 on 2026-08-25.
If it turns out a build is failing, that failure is the real card and this one closes into it. If deployments simply resumed on their own, close this and the epic's verification continues.
Re-check command
curl -s https://objectstack.ai/ | grep -o 'data-dpl-id="[^"]*"'
Any id other than dpl_2nfWjGjSwZjakVEmUG1kBWD6697r means it moved.
Measurement
https://objectstack.aiis serving deploymentdpl_2nfWjGjSwZjakVEmUG1kBWD6697r. That id is unchanged across 19 merges tomain, four of which touchedapps/docs, over roughly two hours.The live generation can be dated precisely by what it does and does not contain:
/robots.txt+/sitemap.xml(16:31)/foo.txt→ 404)<h1>per page (16:57)/docs/data-modeling/objectsstill renders 2<h1>ObjectStack — Apps small enough for AI to hold whole.X-Robots-Tagon agent-reader copiesmetadataBase+ canonicalSo production is pinned to a build made between 16:52 and 16:57 on 2026-08-25.
Control: this is not CDN staleness that a request can defeat.
Cache-Control: no-cache/Pragma: no-cacherequest headers and a cache-busting query string both still returnx-vercel-cache: HITwith an age of 6510s, and thedata-dpl-idembedded in the HTML — which is a property of the build, not of the cache entry — has not moved.Why it matters
Five merged PRs from epic #12243 are invisible to users and to crawlers, and the epic's definition of done is written against the live site, so it cannot be verified while this holds. Three of its five boxes were ticked against production earlier today; the rest cannot be.
What is needed, and why it is not a PM action
Everything visible from GitHub is green: all five PRs merged through the merge queue with full CI. Whatever is stuck is on the Vercel side — a failing production build, a paused project, a promotion that is not happening — and reading that requires the Vercel dashboard or API token for the docs project. No agent in this repo has it.
Maintainer action: check the docs project's deployment list for a failed or queued production build since ~16:55 on 2026-08-25.
If it turns out a build is failing, that failure is the real card and this one closes into it. If deployments simply resumed on their own, close this and the epic's verification continues.
Re-check command
Any id other than
dpl_2nfWjGjSwZjakVEmUG1kBWD6697rmeans it moved.