Bug Graveyard: where fixed bugs are buried, and regressions rise as zombies

This is a submission for the Sanity Challenge, Path Two: Vibe-Code Something Strange

🪦 TL;DR for judges

• Write-up (quality and honesty): My Build Process has the prompts that worked, the one that didn't, every place it got stuck, and what's not live. The full Claude Code session is embedded below.
• Working app: the live site needs no login. Open a zombie's past lives, check Most Haunted, and report a dead bug yourself: an AI coroner drafts its epitaph within seconds.
• Schema: a zombie is a whole new bug that points to its previous life, "disturbed" graves are worked out in GROQ, and AI suggestions and public reports sit in separate fields until a person approves them. See Sanity Project Details.
• Creativity: regressions rise from their graves as zombies, and an AI coroner writes the epitaphs (but never gets the last word).
• Beyond the Studio (bonus): custom Studio actions, a live Tombstone view and sidebar · the Morgue, an App SDK app · two Sanity Functions (a daily gravedigger and the coroner) · an Agent Action (Prompt) · a Workflows experiment on a branch (not live).

A 90-second tour: the site, the Studio's lifecycle actions and Tombstone view, the AI coroner and the Morgue. The Studio scenes use temporary test bugs, deleted afterwards.

What I Built

Bug Graveyard is a memorial site for the bugs we fixed.

Every fixed bug gets a tombstone with its dates, cause of death and an epitaph. Most of them stay dead. But some come back (a regression), and when they do, they rise from their grave as a zombie, linked to the life they had before. The old grave is left disturbed and empty.

A few of the residents:

The 0.1 + 0.2 invoice: "Owed ₹0.30000000000000004. Paid in full."

Timezone bug in scheduler (Zombie #2): "Every time zone. Every time."

<<<<<<< HEAD in production: "Both versions were right. Neither survived."

The graves are classic bugs that every developer has met at some point: off-by-one errors, 0.1 + 0.2, the div that won't centre. They aren't a record of my own personal disasters, and their dates are made up but realistic.

The idea is one joke taken literally: a regression is a bug that came back from the dead, so here it comes back as a zombie. Most of the work went into modelling that lifecycle properly in Sanity, not just drawing tombstones.

Demo

🪦 Live site: https://bug-graveyard.vercel.app

The graveyard shows three kinds of stone:

• Resting: fixed, and it stayed fixed.
• Disturbed: knocked over, with a crossed-out R.I.P. and an empty hole. The bug rose again.
• Zombie: cracked, glowing green, "Risen" and "still walking".

You can filter the graves by language or cause of death. Click any stone to open its grave page: a death certificate (cause of death, severity, hours to kill, killed by) and its past lives. The timezone bug is on its third life, and each life starts on a real daylight-saving switch (30 March 2025, 26 October 2025 and 29 March 2026), because of course it does.

The Most Haunted leaderboard ranks the deadliest bugs (by the hours it took to kill them), the languages with the most zombies, the most common causes of death and the most resurrected chain.

Try it: report a dead bug

The report page lets anyone add a bug. It becomes a suspected-dead bug, the coroner drafts its epitaph within seconds, and it waits under "Awaiting the coroner's approval" until I accept it in the Studio. Only then does it join the graveyard.

The report page with a test report (deleted afterwards).

Every report costs an AI credit, so the form is guarded like any public form that costs money:

• a honeypot field that bots fill in and people never see;
• 3 reports per visitor and 25 in total a day, counted in private documents (a dot in the ID keeps them out of the public API), with the visitor's IP stored only as a keyed hash;
• length limits, no links, and a profanity filter on both the reports and the AI's drafts before they're shown.

The daily cap keeps a month at 25 × 31 = 775 credits at most (plus a rare retry), under the 1,000 free AI credits.

Inside the Studio

This is where most of the Sanity work lives.

1. A bug's life, as custom document actions. A bug moves through 💀 suspected dead → 🩹 fix merged → 🪦 buried. Three custom document actions drive it, and they sit right after Publish in the document's "…" menu:

• 🩹 Mark fix merged sets the status and stamps today's date (in UTC) as the fix date.
• 🪦 Declare buried stays disabled until the fix has held for 7 days. Until then its label is a countdown like "Can bury in 4 days".
• 🧟 Report resurrection asks "Are you sure? This bug will rise from its grave.", then creates a new, already published zombie linked to the old grave, and opens it so you can write its epitaph.

A (temporary) bug whose fix merged 3 days ago: it can't be buried yet, but it can still come back.

2. A live Tombstone view. Every bug opens with two tabs, "Editor" and "🪦 Tombstone". The Tombstone tab renders the same React component the website uses. In split pane the stone updates on every keystroke, with an epitaph counter (140 characters max).

The Studio in split pane: the form on the left, the live 🪦 Tombstone view on the right. (This is a throwaway test bug, deleted afterwards.)

3. A graveyard sidebar: 🪦 All graves, 🗳️ Public reports, 🧟 Zombies, 💀 Suspected dead, 🩹 Fix merged and ⚰️ Buried, then Languages and Causes of death.

Code

💻 Repository: https://github.com/jashanpreet-k/bug-graveyard

Where to look:

• sanity/actions/lifecycle.tsx: the three document actions
• sanity/schemaTypes/bug.ts: the bug schema
• sanity/lib/queries.ts: every GROQ query, typed with Sanity TypeGen
• sanity/components/TombstoneView.tsx and components/Tombstone.tsx: the Studio view and the stone it shares with the site
• apps/morgue/: the Morgue, an App SDK app (see below)
• functions/ and sanity.blueprint.ts: the gravedigger and coroner Sanity Functions (see below)
• app/(site)/report/: the public report page and its server action (all the checks above)
• NOTES.md: the phase-by-phase build log this post is based on

My Build Process

I built Bug Graveyard with Claude Code (in VS Code), one phase at a time: setup, schema, homepage, grave page, first deploy, lifecycle actions, the Studio view, the leaderboard and importer, content, and a polish pass. For each phase I wrote the brief, tested the result in the browser, and decided what to keep or change. Claude Code wrote most of the code, ran the builds, tests and deploys, and added an entry to a build log (NOTES.md) at the end of every phase.

Stack: Next.js 16 (App Router, TypeScript, Tailwind CSS v4), Sanity Studio v5 embedded at /studio, next-sanity, deployed on Vercel.

The prompts that worked

Short phase briefs with explicit rules and a test step. Here's part of the Phase 5 brief, for the lifecycle actions:

2. "🪦 Declare buried": enabled only when status = fix-merged AND at least 7 days have passed since fixMergedAt. When disabled, the label/title says how many days are left (e.g. "Can bury in 4 days"). Sets status = buried and buriedAt = today, then publishes.

Rules:

• Use dates in UTC like the rest of the app.
• Handle drafts correctly (act on the published doc, don't leave stray drafts).
• Make the 7-day rule a single constant so I can mention it in the write-up.

Test it end to end with temporary test bugs (delete them after) …

Claude Code tested that phase against a production build, with headless Chrome clicking the real Studio buttons: 34 checks across five temporary bugs, which were all deleted afterwards. It also went beyond the brief in a couple of places, and I kept those changes. My brief said each action should "then publish". Instead, the actions write straight to the published document in one change guarded by its revision, and they're disabled while the bug has unpublished edits, because that draft would later overwrite the new status. And "Mark fix merged" also works on a zombie, so a zombie can start a lifecycle of its own.

The one that didn't

Before the polish pass, I asked Claude Code to look through the other projects on my Mac for bugs I'd really fixed, so that a few graves could be real. It found no bug-fix commits to use. So I dropped that and kept the classic bugs.

Where it got stuck, and how we course-corrected

Most of these only showed up in a production build or on the live site, not in npm run dev.

• Publishing didn't reach the site. In a production build, publishing from the Studio didn't update the site, and an open tab stayed one change behind. There were two causes. The Studio route had no <SanityLive /> to clear the cache, and in production next-sanity revalidates with the 'max' cache profile, which serves the stale page one more time. The fix: <SanityLive /> in the Studio layout too, plus a custom action that calls updateTag, which expires the cache immediately. npm run dev hid both problems.
• The first Vercel deploy failed with No Output Directory named "dist" found. The Vercel project had been created with the "Other" framework preset. A vercel.json that sets "framework": "nextjs" fixed it.
• Scripts silently skipped drafts. With this API version, a query that doesn't name a perspective gets published, so a cleanup script would never have found drafts.* documents. Scripts that need drafts now ask for raw.
• "Report resurrection" flickered disabled. Its "has this grave already risen?" check restarted every time the document changed, and it blocked the button while it ran. Now the button is only disabled once a zombie is known to exist, and it checks again when you confirm.
• The site's CSS leaked into the Studio. The root 404 page imported the site's global CSS, and a root not-found page's styles load on every route, so Tailwind ended up inside /studio. A scoped CSS module fixed it.
• The build prerendered deleted bugs. generateStaticParams read the slug list from Next's local fetch cache, which still held old test bugs. It now fetches the slugs with cache: 'no-store'.

Two traps we avoided on purpose:

• The timezone bug could have had a timezone bug. Sanity date fields are plain strings like "2026-03-29", with no timezone. Formatting them in the visitor's timezone would make every bug die a day early for anyone west of Greenwich, including on the timezone bug's own tombstone. So every date is formatted in UTC.
• A dot in a document ID makes it private. Sanity treats a dotted ID as a private path (that's how drafts. works), so a public dataset won't serve language.typescript without a token. The seed used dashed IDs like language-typescript from the start. A quick test while writing this post confirmed it: a published document with a dotted ID didn't appear in a public query.

Reaching past the Studio: Workflows

I also asked Claude Code to find out, in a 3-hour time box, whether Sanity Workflows could run this lifecycle. It can model it. On a separate branch (explore/workflows), the lifecycle is two workflow definitions (one for a bug and one for a zombie), and "Declare buried" is gated by a GROQ requirement instead of a timer:

dateTime($now) >= dateTime($fields.fixMergedAt) + 604800 // 7 days, in seconds

npx sanity-workflows deploy --check passes for both definitions, and 4 tests pass against the real engine running in memory with a controlled clock. Burial is refused until exactly 7 days have passed.

I didn't merge it. Workflows is in early access (0.35), its Studio plugin needs Studio 6 while this project runs Studio 5, and effects need a runtime I'd have to run myself. A proper integration also means deciding whether the workflow or the bug's own status field is the source of truth, which Claude Code estimated at 1.5 to 2 days. The live site still runs on the document actions.

Reaching past the Studio: the App SDK

After publishing this post, I had Claude Code build the Morgue: a small App SDK app that runs in the Sanity Dashboard. It shows every bug that isn't resting yet in four live columns: suspected dead, walking, waiting and ready to bury. Each card has the same three lifecycle actions as the Studio, with the same rules, because both import the same sanity/lib/lifecycle.ts.

The Morgue running locally in the Sanity Dashboard, with temporary test bugs that were deleted afterwards. No refresh anywhere: the cards move as the documents change.

• Everything is live. Each column is a useDocuments list with a GROQ filter, and each card reads its fields with useDocumentProjection.
• The buttons are the Studio's actions, rebuilt with the App SDK. They use useApplyDocumentActions with editDocument and createDocument on liveEdit handles, which write straight to the published bug like the Studio's actions do. They also wait while a bug has unpublished Studio changes.
• Tested in the real Dashboard: 18 checks on temporary test bugs, all deleted afterwards.
• One surprise: the Sanity CLI looks for a Studio config in every parent folder before it looks for an app config. Inside this repo, whose root holds the embedded Studio's config, sanity build built the site's Studio instead. The app's npm scripts now run the CLI from a mirror folder outside the repo.

The code is in apps/morgue. It's deployed to my organization's Sanity Dashboard, which only members of the organization can open, so for judges the GIF and the code are what's visible.

Reaching past the Studio: Functions & the AI Coroner

Next came two Sanity Functions, deployed with a Blueprint:

• The gravedigger is a scheduled function that runs every day at 00:15 UTC. It buries every bug whose fix has held for 7 days, using the same rules file as the Studio's "Declare buried" and the Morgue, and it skips bugs with unpublished Studio changes. (Once a day is also the most often a scheduled function can run on the Free plan.)
• The coroner is a document function. When a bug is published as suspected dead with no epitaph, it asks an Agent Action (Prompt) for a short epitaph in the style of the existing graves, plus a cause of death chosen from the real ones. It writes that only into separate coroner… fields, marked "awaiting approval".
• A person decides. A new ✅ Accept coroner's report document action shows the suggestion and copies it into the real fields only when you click Accept. The AI never touches the real epitaph and never publishes anything on its own.

A coroner's report waiting for approval. The bugs in the list are temporary test bugs that were deleted afterwards.

The coroner also drafts the epitaphs of bugs reported on the site. Its prompt treats the reporter's words only as a description of the bug, never as instructions, and nothing it writes is shown publicly without the profanity check.

Both functions were tested with Sanity's local runner against the real dataset first: 23 checks on temporary bugs, including a forced gravedigger run. Then the deployed coroner filed its first report in the cloud about 4.5 seconds after a test bug was published.

Sanity Project Details

• Project ID: rzjmw6lg
• Dataset: production (public). Try it: every bug, as JSON

There are three document types: bug, language and causeOfDeath. Here's how everything reaches them:

The schema: zombies are documents, not checkboxes

The central decision: a zombie is a whole new bug document that points to its previous life. It isn't a status flag on the old one.

// sanity/schemaTypes/bug.ts (simplified)
defineField({
  name: 'status',
  type: 'string',
  options: {list: ['suspected-dead', 'fix-merged', 'buried', 'zombie']},
}),
defineField({
  name: 'previousLife',
  type: 'reference',
  to: [{type: 'bug'}],
  hidden: ({document}) => document?.status !== 'zombie',
}),
defineField({name: 'timesResurrected', type: 'number', readOnly: true}),

Why:

• Every death keeps its own history. A zombie gets fixed and buried again, so it needs its own dates and its own epitaph.
• Zombies of zombies work for free. A chain is just references pointing backwards.
• "Disturbed" isn't stored anywhere. GROQ works it out by asking whether any bug points at this one:

*[_type == "bug"]{
  ...,
  "disturbed": count(*[_type == "bug" && previousLife._ref == ^._id]) > 0
}

• Languages and causes of death are references, so filters and the leaderboard count them reliably. The whole leaderboard is one GROQ query.
• The fix date, the burial date and the resurrection counter are read-only in the Studio. There, only the lifecycle actions set them, so they record what actually happened rather than what someone typed. (readOnly only applies to the Studio: the importer script sets historical dates from a file.)

How document actions work

Every button at the bottom of a Sanity document (Publish, Delete…) is a document action, and you can add your own. An action is a small React component: Sanity passes it the document's current state and it returns a button (label, disabled, tooltip, onHandle, optional confirm dialog). You register actions in sanity.config.ts. Because an action is a component, it re-renders whenever the document changes, which is how "Can bury in 4 days" stays up to date without any extra code. Actions run in the browser as the signed-in editor, with their permissions, so there's no API token in the code.

Live everywhere

sanityFetch plus <SanityLive /> push Studio edits to open tabs in about 3 seconds. A signed Sanity webhook refreshes the cached site when nobody has it open (about 6 seconds).

Agent Session

This is the Claude Code session behind this build, with secrets redacted. The embed shows the Phase 5 slice, where the lifecycle document actions were built and tested. The full session has every phase.

Building Bug Graveyard (Next.js + Sanity) with Claude Code claude-opus-5-5

You

Phase 5: add custom Sanity document actions that model a bug's lifecycle, and fill in the
read-only fields (fixMergedAt, buriedAt, timesResurrected) that nothing sets yet.

Actions on the bug type (register them in sanity.config.ts via document.actions, keep the
default Publish/Delete etc.):

1. "🩹 Mark fix merged": enabled only when status = suspected-dead. Sets status = fix-merged and fixMergedAt = today, then publishes.
2. "🪦 Declare buried": enabled only when status = fix-merged AND at least 7 days have passed since fixMergedAt. When disabled, the label/title says how many days are left (e.g. "Can bury in 4 days"). Sets status = buried and buriedAt = today, then publishes.
3. "🧟 Report resurrection": enabled when status = fix-merged or buried. Creates a NEW bug document: status = zombie, previousLife = this bug, timesResurrected = old + 1, name = "<original name> (Zombie #n)", same language/cause, a new unique slug, bornAt = today. Then open the new zombie in the Studio so I can write its epitaph. Show a confirm dialog first: "Are you sure? This bug will rise from its grave."

Rules:
- Use dates in UTC like the rest of the app.
- Handle drafts correctly (act on the published doc, don't leave stray drafts).
- A zombie can later go through the same lifecycle (fix merged → buried → resurrect again),
so zombies of zombies work.
- Make the 7-day rule a single constant so I can mention it in the write-up.

Test it end to end with temporary test bugs (delete them after), confirm the homepage and
grave pages update live, then run build/lint/type-check, add the Phase 5 entry to NOTES.md,
commit and deploy. Also explain in plain words how document actions work in Sanity, for my
write-up.

Show more

Agent

Phase 5 is Studio code, so I'll start with the document action API in the installed Sanity 5.31: the props an action receives, what it can return (label, disabled, title, confirm dialog), and how to register actions and open another document.

Agent

▸ Bash f=$(grep -l "interface DocumentActionProps" node_modules/sanity/lib/*.d.ts no...

Input

$ f=$(grep -l "interface DocumentActionProps" node_modules/sanity/lib/*.d.ts node_modules/sanity/lib/_chunks-dts/*.d.ts 2>/dev/null | head -1); echo "defs in: $f"; for n in "interface DocumentActionProps" "interface DocumentActionDescription" "interface DocumentActionConfirmDialogProps" "interface DocumentActionDialogDialogProps" "type DocumentActionDialogProps" "interface DocumentActionComponent" "type DocumentActionsResolver" "interface DocumentActionsContext"; do echo "=================== $n"; awk -v pat="$n" 'index($0, pat) {p=1} p {print; if (/^}/ || (/;$/ && pat ~ /^type/)) {exit}}' "$f" | grep -v "^\s*\*\|/\*\*" | head -30; done

Output

defs in: node_modules/sanity/lib/_chunks-dts/ActiveWorkspaceMatcherContext.d.ts
=================== interface DocumentActionProps
interface DocumentActionProps extends EditStateFor {
  revision?: string;
  onComplete: () => void;
  initialValueResolved: boolean;
}
=================== interface DocumentActionDescription
interface DocumentActionDescription extends GroupableActionDescription<DocumentActionGroup> {
  dialog?: DocumentActionDialogProps | false | null;
}
=================== interface DocumentActionConfirmDialogProps
interface DocumentActionConfirmDialogProps {
  type: 'confirm';
  tone?: ButtonTone;
  message: ReactNode;
  onConfirm: () => void;
  onCancel: () => void;
  cancelButtonIcon?: ComponentType | ReactNode;
  cancelButtonText?: string;
  confirmButtonIcon?: ComponentType | ReactNode;
  confirmButtonText?: string;
}
=================== interface DocumentActionDialogDialogProps
=================== type DocumentActionDialogProps
type DocumentActionDialogProps = DocumentActionConfirmDialogProps | DocumentActionPopoverDialogProps | DocumentActionModalDialogProps | DocumentActionCustomDialogComponentProps;
=================== interface DocumentActionComponent
interface DocumentActionComponent extends ActionComponent<DocumentActionProps, DocumentActionDescription> {
  action?: keyof DocumentActionKeys;
  displayName?: string;
}
=================== type DocumentActionsResolver
type DocumentActionsResolver = ComposableOption<DocumentActionComponent[], DocumentActionsContext>;
=================== interface DocumentActionsContext
interface DocumentActionsContext extends ConfigContext$1 {
  documentId?: string;
  schemaType: string;
  releaseId: string | undefined;
  versionType: DocumentActionsVersionType;
}

Agent

▸ Bash f=node_modules/sanity/lib/_chunks-dts/ActiveWorkspaceMatcherContext.d.ts; for...

Input

$ f=node_modules/sanity/lib/_chunks-dts/ActiveWorkspaceMatcherContext.d.ts; for n in "interface EditStateFor" "interface GroupableActionDescription" "interface DocumentActionModalDialogProps" "type DocumentActionsVersionType" "interface ActionComponent<"; do echo "=================== $n"; awk -v pat="$n" 'index($0, pat) {p=1} p {print; if (/^}/ || (/;$/ && pat ~ /^type/)) {exit}}' "$f" | grep -v "^\s*\*\|/\*\*\|^\s*\*/" | head -26; done; echo "=== exports of interest"; for n in useClient useDocumentStore useDocumentOperation useCurrentUser getPublishedId getDraftId isDraftId useToast; do printf "%-22s %s\n" $n "$(grep -c "\b$n\b" node_modules/sanity/lib/index.d.ts)"; done; grep -o "navigateIntent[^;]*;" node_modules/sanity/lib/_chunks-dts/*.d.ts node_modules/sanity/lib/router.d.ts 2>/dev/null | head -2

Output

=================== interface EditStateFor
interface EditStateFor {
  id: string;
  type: string;
  transactionSyncLock: TransactionSyncLockState | null;
  draft: SanityDocument | null;
  published: SanityDocument | null;
  version: SanityDocument | null;
  liveEdit: boolean;
  liveEditSchemaType: boolean;
  ready: boolean;
  release: string | undefined;
}
=================== interface GroupableActionDescription
interface GroupableActionDescription<GroupType = unknown> extends BaseActionDescription {
  group?: GroupType[];
}
=================== interface DocumentActionModalDialogProps
interface DocumentActionModalDialogProps {
  type?: 'dialog';
  content: ReactNode;
  footer?: DialogProps['footer'];
  header?: ReactNode;
  onClose: () => void;
  showCloseButton?: boolean;
  width?: 'small' | 'medium' | 'large' | 'full';
}
=================== type DocumentActionsVersionType
type DocumentActionsVersionType = 'published' | 'draft' | 'revision' | 'version' | 'scheduled-draft';
=================== interface ActionComponent<
interface ActionComponent<ActionProps, ActionDescription> {
  (props: ActionProps): ActionDescription | null;
}
=== exports of interest
useClient              2
useDocumentStore       2
useDocumentOperation   2
useCurrentUser         2
getPublishedId         2
getDraftId             2
isDraftId              2
useToast               0
node_modules/sanity/lib/_chunks-dts/types3.d.ts:navigateIntent: (intentName: string, params?: IntentParameters, options?: NavigateBaseOptions) => void;

Agent

▸ Bash f=node_modules/sanity/lib/_chunks-dts/ActiveWorkspaceMatcherContext.d.ts; awk...

Input

$ f=node_modules/sanity/lib/_chunks-dts/ActiveWorkspaceMatcherContext.d.ts; awk 'index($0, "interface BaseActionDescription") {p=1} p {print; if (/^}/) exit}' $(grep -l "interface BaseActionDescription" node_modules/sanity/lib/_chunks-dts/*.d.ts | head -1) | grep -v "^\s*\*\|/\*\*\|^\s*\*/"; echo "=== listenQuery"; grep -h -o "listenQuery: ([^;]*;" node_modules/sanity/lib/_chunks-dts/*.d.ts | head -2; grep -h -B2 -A8 "interface ListenQueryOptions" node_modules/sanity/lib/_chunks-dts/*.d.ts | grep -v "^\s*\*\|/\*\*\|^\s*\*/" | head -14

Output

interface BaseActionDescription {
  disabled?: boolean;
  icon?: ReactNode | ComponentType;
  label: string;
  onHandle?: () => void;
  title?: ReactNode;
  tone?: ButtonTone;
  shortcut?: string | null;
  dialog?: unknown;
}
=== listenQuery
interface ListenQueryOptions {
  tag?: string;
  apiVersion?: string;
  perspective?: ClientPerspective;
  throttleTime?: number;
  transitions?: ('update' | 'appear' | 'disappear')[];
}
declare function listenQuery(client: SanityClient, query: string | {

Agent

▸ Bash grep -h -A6 "declare function listenQuery" node_modules/sanity/lib/_chunks-dt...

Input

$ grep -h -A6 "declare function listenQuery" node_modules/sanity/lib/_chunks-dts/*.d.ts | head -10; grep -c "listenQuery" node_modules/sanity/lib/index.d.ts; grep -oE "[A-Za-z_$0-9]+ as listenQuery\b" node_modules/sanity/lib/index.d.ts | head -2; grep -h -B3 -A12 "interface DocumentStore {" node_modules/sanity/lib/_chunks-dts/*.d.ts | grep -iE "listenQuery|interface DocumentStore" | head

Output

declare function listenQuery(client: SanityClient, query: string | {
  fetch: string;
  listen: string;
}, params?: ListenQueryParams, options?: ListenQueryOptions): Observable<any>;
/**
 * @hidden
 * @beta */
2
ugrep: error: error at position 21
(?m)[A-Za-z_/bin/zsh-9]+ as listenQuery\b
                     \___invalid character class range


interface DocumentStore {
  listenQuery: (query: string | {

Agent

▸ Bash grep -rhoE "__studio_auth_token[^\"'\`]{0,40}" node_modules/sanity/lib/ 2>/de...

Input

$ grep -rhoE "__studio_auth_token[^\"'\`]{0,40}" node_modules/sanity/lib/ 2>/dev/null | sort -u | head -5; f=$(grep -rl "__studio_auth_token" node_modules/sanity/lib/_chunks-es/*.js 2>/dev/null | head -1); echo "file: $f"; grep -oE ".{200}__studio_auth_token.{300}" "$f" | head -2

Output

__studio_auth_token_
file: 
ugrep: warning: : No such file or directory

Agent

▸ Bash f=$(grep -rl "__studio_auth_token_" node_modules/sanity/lib/ 2>/dev/null | he...

Input

$ f=$(grep -rl "__studio_auth_token_" node_modules/sanity/lib/ 2>/dev/null | head -3); echo "$f"; for x in $f; do grep -oE ".{0,250}__studio_auth_token_.{0,250}" "$x" | head -3; done | cut -c1-600

Output

node_modules/sanity/lib/index.js
node_modules/sanity/lib/index.js.map
ugrep: warning: node_modules/sanity/lib/index.js
node_modules/sanity/lib/index.js.map: No such file or directory

Agent

Still in Phase 5 prep. I've mapped the document action API and am checking how to sign in a headless Studio for tests. Next I'll write the lifecycle actions.

Agent

▸ Bash grep -oE ".{0,200}__studio_auth_token_.{0,300}" node_modules/sanity/lib/index...

Input

$ grep -oE ".{0,200}__studio_auth_token_.{0,300}" node_modules/sanity/lib/index.js | head -3 | cut -c1-520

Output

ugrep: error: error at position 98
_(?:[^\n\x80-\xbf][\x80-\xbf]*){0,300}
         exceeds complexity limits___/

Agent

▸ Bash node -e ' const s = require("fs").readFileSync("node_modules/sanity/lib/index...

Input

$ node -e '
const s = require("fs").readFileSync("node_modules/sanity/lib/index.js", "utf8")
let i = -1, n = 0
while ((i = s.indexOf("__studio_auth_token_", i + 1)) !== -1 && n++ < 3) console.log("---\n" + s.slice(Math.max(0, i - 260), i + 320))
'

Output

---
025-02-19"
}, DEFAULT_STUDIO_CLIENT_HEADERS = {
  "x-sanity-app": `studio@${SANITY_VERSION}`
}, versionedClient = (client, apiVersion) => apiVersion ? client.withConfig({
  apiVersion
}) : client, AUTH_API_VERSION = "v2026-05-04", AUTH_TOKEN_STORAGE_PREFIX = "__studio_auth_token_", COOKIE_AUTH_STATE_PREFIX = "__studio_auth_cookie_state_", UNAUTHENTICATED = {
  authenticated: !1
}, AUTHENTICATED = {
  authenticated: !0
}, AUTH_CLIENT_OPTIONS = {
  apiVersion: AUTH_API_VERSION,
  useCdn: !1,
  perspective: "raw",
  requestTagPrefix: "sanity.studio",
  allowReconfigure: !1,

Agent

▸ Bash node -e ' const s = require("fs").readFileSync("node_modules/sanity/lib/index...

Input

$ node -e '
const s = require("fs").readFileSync("node_modules/sanity/lib/index.js", "utf8")
for (const needle of ["AUTH_TOKEN_STORAGE_PREFIX}", "AUTH_TOKEN_STORAGE_PREFIX +", "getToken(projectId", "function getStorageKey", "localStorage.getItem("]) {
  let i = -1, n = 0
  while ((i = s.indexOf(needle, i + 1)) !== -1 && n++ < 2) console.log("--- [" + needle + "]\n" + s.slice(Math.max(0, i - 200), i + 260))
}
' | head -60

Output

--- [AUTH_TOKEN_STORAGE_PREFIX}]
,
  useCdn: !1,
  perspective: "raw",
  requestTagPrefix: "sanity.studio",
  allowReconfigure: !1,
  headers: DEFAULT_STUDIO_CLIENT_HEADERS
};
function getAuthTokenStorageKey(projectId) {
  return `${AUTH_TOKEN_STORAGE_PREFIX}${projectId}`;
}
function getCookieAuthStateKey(projectId) {
  return `${COOKIE_AUTH_STATE_PREFIX}${projectId}`;
}
function createLocalStorageStorage(key) {
  function load() {
    try {
      const value = localStorage.getItem(key);

--- [localStorage.getItem(]
-"), localStorage.removeItem(key), !0);
  } catch {
    return !1;
  }
})(), LOCAL_STORAGE_PREFIX = "sanity-locale";
function getPreferredLocale(projectId, sourceId) {
  return supportsLocalStorage ? localStorage.getItem(getItemKey$1(projectId, sourceId)) ?? void 0 : void 0;
}
function storePreferredLocale(projectId, sourceId, locale) {
  supportsLocalStorage && localStorage.setItem(getItemKey$1(projectId, sourceId), locale);
}
function getItemKey$1(projec
--- [localStorage.getItem(]
ctId}`;
}
function getCookieAuthStateKey(projectId) {
  return `${COOKIE_AUTH_STATE_PREFIX}${projectId}`;
}
function createLocalStorageStorage(key) {
  function load() {
    try {
      const value = localStorage.getItem(key);
      return value === null ? void 0 : JSON.parse(value);
    } catch (err) {
      console.error(`Failed to parse localstorage value: ${err.message}`);
      return;
    }
  }
  function store(value) {
    try {
      value === void

Agent

▸ Bash node -e ' const s = require("fs").readFileSync("node_modules/sanity/lib/index...

Input

$ node -e '
const s = require("fs").readFileSync("node_modules/sanity/lib/index.js", "utf8")
for (const needle of ["getAuthTokenStorageKey(", "loginMethod"]) {
  let i = s.indexOf("function getAuthTokenStorageKey") + 50, n = 0
  i = -1
  while ((i = s.indexOf(needle, i + 1)) !== -1 && n++ < 4) console.log("--- [" + needle + "]\n" + s.slice(Math.max(0, i - 150), i + 250).replace(/\n\s+/g, " "))
}
' | head -40

Output

--- [getAuthTokenStorageKey(]
  useCdn: !1, perspective: "raw", requestTagPrefix: "sanity.studio", allowReconfigure: !1, headers: DEFAULT_STUDIO_CLIENT_HEADERS
};
function getAuthTokenStorageKey(projectId) { return `${AUTH_TOKEN_STORAGE_PREFIX}${projectId}`;
}
function getCookieAuthStateKey(projectId) { return `${COOKIE_AUTH_STATE_PREFIX}${projectId}`;
}
function createLocalStorageStorage(key) { function load() {
--- [getAuthTokenStorageKey(]
", getSessionId: getSessionId2, consumeHashToken: consumeHashToken2, ...providerOptions
}) { const tokenStorage = createBroadcastStorage( getAuthTokenStorageKey(projectId), // sets the initial value (currentTokenValue) => { const hashToken = consumeHashToken2(); return hashToken ? { token: hashToken, authenticated: !0 } : currentTokenValue; 
--- [getAuthTokenStorageKey(]
: "\u2022" }) ] }, link.title);
}
function getStoredToken(projectId) { if (supportsLocalStorage) try { const raw = localStorage.getItem(getAuthTokenStorageKey(projectId)); return raw ? JSON.parse(raw)?.token : void 0; } catch { return; }
}
function resolveApiHost(apiHost) { if (apiHost) return apiHost; if (isStaging) return "https://api.sanity.work";
}
async f
--- [getAuthTokenStorageKey(]
.token ? { token, ignoreBrowserTokenWarning: !0 } : { withCredentials: !0 } }, client = factory(clientConfig), tokenKey = getAuthTokenStorageKey(input.projectId), cookieKey = getCookieAuthStateKey(input.projectId), observable$ = using(() => { const cookieState = token ? null : createBroadcastState(cookieKey); return { cookieState, unsubscribe: () => 
--- [loginMethod]
filter((official) => customProviders.some((provider) => provider.url !== official.url)).concat(customProviders);
}
function createHrefForProvider({ loginMethod = "dual", projectId, url, redirectPath
}) { const params = new URLSearchParams(); return params.set("origin", `${window.location.origin}${redirectPath}`), params.set("projectId", projectId), loginMethod === "token" ? params.set(
--- [loginMethod]
 const params = new URLSearchParams(); return params.set("origin", `${window.location.origin}${redirectPath}`), params.set("projectId", projectId), loginMethod === "token" ? params.set("withSid", "true") : params.set("type", loginMethod), `${url}?${params}`;
}
function createLoginComponent({ client$, loginMethod, redirectOnSingle, wasLogout, isHandlingCallback, ...providerOptions
}) 
--- [loginMethod]
w.location.origin}${redirectPath}`), params.set("projectId", projectId), loginMethod === "token" ? params.set("withSid", "true") : params.set("type", loginMethod), `${url}?${params}`;
}
function createLoginComponent({ client$, loginMethod, redirectOnSingle, wasLogout, isHandlingCallback, ...providerOptions
}) { function LoginComponent(t0) { const $ = c(28), { projectId, 
--- [loginMethod]
hod === "token" ? params.set("withSid", "true") : params.set("type", loginMethod), `${url}?${params}`;
}
function createLoginComponent({ client$, loginMethod, redirectOnSingle, wasLogout, isHandlingCallback, ...providerOptions

Agent

▸ Write /Users/jashanpreetkaur/Desktop/bug-graveyard/sanity/lib/lifecycle.ts

Input

/Users/jashanpreetkaur/Desktop/bug-graveyard/sanity/lib/lifecycle.ts

Output

File created successfully at: /Users/jashanpreetkaur/Desktop/bug-graveyard/sanity/lib/lifecycle.ts (file state is current in your context — no need to Read it back)

Agent

Before building on these helpers I'll check them quickly with Node's built-in TypeScript support, including a late-evening IST time that is still the previous day in UTC.

Agent

▸ Bash node --input-type=module -e ' import {BURIAL_WAIT_DAYS, daysUntilBurial, zomb...

Input

$ node --input-type=module -e '
import {BURIAL_WAIT_DAYS, daysUntilBurial, zombieName, slugify, todayUTC, daysBetween} from "./sanity/lib/lifecycle.ts"
const eq = (label, got, want) => console.log(`${JSON.stringify(got) === JSON.stringify(want) ? "ok  " : "FAIL"} ${label}: ${JSON.stringify(got)}`)
eq("BURIAL_WAIT_DAYS", BURIAL_WAIT_DAYS, 7)
eq("fixed today -> 7 days left", daysUntilBurial("2026-09-29", "2026-09-29"), 7)
eq("fixed 3 days ago -> 4 left", daysUntilBurial("2026-09-26", "2026-09-29"), 4)
eq("fixed 7 days ago -> 0 left", daysUntilBurial("2026-09-22", "2026-09-29"), 0)
eq("fixed 30 days ago -> 0 left", daysUntilBurial("2026-08-30", "2026-09-29"), 0)
eq("across a month end", daysBetween("2026-02-27", "2026-03-02"), 3)
eq("01:30 IST on the 29th is still the 28th in UTC", todayUTC(new Date("2026-09-29T01:30:00+05:30")), "2026-09-28")
eq("first zombie", zombieName("Timezone bug in scheduler", 1), "Timezone bug in scheduler (Zombie #1)")
eq("zombie of a zombie keeps the original name", zombieName("Timezone bug in scheduler (Zombie #1)", 2), "Timezone bug in scheduler (Zombie #2)")
eq("slug", slugify("Timezone bug in scheduler (Zombie #2)"), "timezone-bug-in-scheduler-zombie-2")
eq("slug with accents and symbols", slugify("  Crème brûlée: C++ bug!! "), "creme-brulee-c-bug")
' 2>&1 | grep -v ExperimentalWarning

Output

(node:24361) [MODULE_TYPELESS_PACKAGE_JSON] Warning: Module type of file:///Users/jashanpreetkaur/Desktop/bug-graveyard/sanity/lib/lifecycle.ts is not specified and it doesn't parse as CommonJS.
Reparsing as ES module because module syntax was detected. This incurs a performance overhead.
To eliminate this warning, add "type": "module" to /Users/jashanpreetkaur/Desktop/bug-graveyard/package.json.
(Use `node --trace-warnings ...` to show where the warning was created)
ok   BURIAL_WAIT_DAYS: 7
ok   fixed today -> 7 days left: 7
ok   fixed 3 days ago -> 4 left: 4
ok   fixed 7 days ago -> 0 left: 0
ok   fixed 30 days ago -> 0 left: 0
ok   across a month end: 3
ok   01:30 IST on the 29th is still the 28th in UTC: "2026-09-28"
ok   first zombie: "Timezone bug in scheduler (Zombie #1)"
ok   zombie of a zombie keeps the original name: "Timezone bug in scheduler (Zombie #2)"
ok   slug: "timezone-bug-in-scheduler-zombie-2"
ok   slug with accents and symbols: "creme-brulee-c-bug"

Agent

▸ Write /Users/jashanpreetkaur/Desktop/bug-graveyard/sanity/actions/lifecycle.tsx

Input

/Users/jashanpreetkaur/Desktop/bug-graveyard/sanity/actions/lifecycle.tsx

Output

File created successfully at: /Users/jashanpreetkaur/Desktop/bug-graveyard/sanity/actions/lifecycle.tsx (file state is current in your context — no need to Read it back)

Agent

▸ Read /Users/jashanpreetkaur/Desktop/bug-graveyard/sanity.config.ts

Input

/Users/jashanpreetkaur/Desktop/bug-graveyard/sanity.config.ts

Output

1   'use client'
2   
3   /**
4    * This configuration is used to for the Sanity Studio that’s mounted on the `/app/studio/[[...tool]]/page.tsx` route
5    */
6   
7   import {visionTool} from '@sanity/vision'
8   import {defineConfig} from 'sanity'
9   import {structureTool} from 'sanity/structure'
10  
11  // Go to https://www.sanity.io/docs/api-versioning to learn how API versioning works
12  import {apiVersion, dataset, projectId} from './sanity/env'
13  import {schema} from './sanity/schemaTypes'
14  import {structure} from './sanity/structure'
15  
16  export default defineConfig({
17    basePath: '/studio',
18    projectId,
19    dataset,
20    // Add and edit the content schema in the './sanity/schemaTypes' folder
21    schema,
22    plugins: [
23      structureTool({structure}),
24      // Vision is for querying with GROQ from inside the Studio
25      // https://www.sanity.io/docs/the-vision-plugin
26      visionTool({defaultApiVersion: apiVersion}),
27    ],
28  })
29

Agent

▸ Edit /Users/jashanpreetkaur/Desktop/bug-graveyard/sanity.config.ts

Input

/Users/jashanpreetkaur/Desktop/bug-graveyard/sanity.config.ts

Output

The file /Users/jashanpreetkaur/Desktop/bug-graveyard/sanity.config.ts has been updated successfully. (file state is current in your context — no need to Read it back)

Agent

▸ Bash npx tsc --noEmit 2>&1 | head -20 && echo "tsc exit: ${pipestatus[1]}"; npm ru...

Input

$ npx tsc --noEmit 2>&1 | head -20 && echo "tsc exit: ${pipestatus[1]}"; npm run lint --silent 2>&1 | tail -20; echo "lint exit: ${pipestatus[1]}"

Output

tsc exit: 0
lint exit: 0

Agent

Type-check and lint are clean. Next I'll check Sanity's own schema validation, whether TypeGen still runs now that sanity/ contains Studio-only code, and the production build.

Agent

▸ Bash npx sanity schemas validate 2>&1 | grep -E "Errors|Warnings|✖|rror" | head -5...

Input

$ npx sanity schemas validate 2>&1 | grep -E "Errors|Warnings|✖|rror" | head -5; npm run typegen 2>&1 | grep -E "✔ Success|queries and|rror|✖" ; git diff --stat sanity/types.ts sanity/extract.json; npm run build 2>&1 | grep -E "Compiled|TypeScript|rror|/studio"

Output

✖ Errors:   0 errors
⚠ Warnings: 0 warnings
✔ Successfully generated types to /Users/jashanpreetkaur/Desktop/bug-graveyard/sanity/types.ts in 382ms
  └─ 4 queries and 17 schema types
✓ Compiled successfully in 944ms
  Running TypeScript ...
  Finished TypeScript in 1112ms ...
└ ○ /studio/[[...tool]]

Agent

▸ Bash SP=/private/tmp/claude-501/-Users-jashanpreetkaur-Desktop-bug-graveyard/0adab...

Input

$ SP=/private/tmp/claude-501/-Users-jashanpreetkaur-Desktop-bug-graveyard/0adab70e-beca-4347-ad08-acf0d3b85074/scratchpad
node --input-type=module -e '
import {writeFileSync} from "node:fs"
const day = (n) => new Date(Date.now() - n * 864e5).toISOString().slice(0, 10)
const ref = (_ref) => ({_type: "reference", _ref})
const bug = (key, extra) => ({
  _id: `test-bug-life-${key}`, _type: "bug", name: `Lifecycle test: ${key}`,
  slug: {_type: "slug", current: `test-bug-life-${key}`},
  language: ref("language-typescript"), causeOfDeath: ref("causeOfDeath-off-by-one"),
  severity: "low", bornAt: day(30), timesResurrected: 0, epitaph: `Temporary: ${key}.`, ...extra,
})
const docs = [
  bug("suspected", {status: "suspected-dead"}),
  bug("waiting", {status: "fix-merged", fixMergedAt: day(3)}),
  bug("ready", {status: "fix-merged", fixMergedAt: day(8)}),
  bug("buried", {status: "buried", fixMergedAt: day(20), buriedAt: day(12)}),
  bug("drafted", {status: "suspected-dead"}),
  {...bug("drafted", {status: "suspected-dead"}), _id: "drafts.test-bug-life-drafted", epitaph: "An unpublished edit."},
]
writeFileSync(process.argv[1], JSON.stringify(docs, null, 2))
' "$SP/life-docs.json"
npx sanity documents create "$SP/life-docs.json" --replace 2>&1 | grep -v "npm warn" | tail -8

Output

Upserted:
  - drafts.test-bug-life-drafted
  - test-bug-life-suspected
  - test-bug-life-waiting
  - test-bug-life-ready
  - test-bug-life-buried
  - test-bug-life-drafted

Agent

▸ Write /private/tmp/claude-501/-Users-jashanpreetkaur-Desktop-bug-graveyard/0adab70e...

Input

/private/tmp/claude-501/-Users-jashanpreetkaur-Desktop-bug-graveyard/0adab70e-beca-4347-ad08-acf0d3b85074/scratchpad/studio-cdp.mjs

Output

File created successfully at: /private/tmp/claude-501/-Users-jashanpreetkaur-Desktop-bug-graveyard/0adab70e-beca-4347-ad08-acf0d3b85074/scratchpad/studio-cdp.mjs (file state is current in your context — no need to Read it back)

Agent

▸ Bash SP=/private/tmp/claude-501/-Users-jashanpreetkaur-Desktop-bug-graveyard/0adab...

Input

$ SP=/private/tmp/claude-501/-Users-jashanpreetkaur-Desktop-bug-graveyard/0adab70e-beca-4347-ad08-acf0d3b85074/scratchpad
cat > "$SP/explore.mjs" <<'EOF'
import {openStudio, wait} from './studio-cdp.mjs'
const [, , port, base, sp] = process.argv
const s = await openStudio(port, base, 'rzjmw6lg')
await s.navigate('/studio/intent/edit/id=test-bug-life-suspected;type=bug')
await s.until('document form', `!!document.querySelector('[data-testid="action-menu-button"]')`, 60000)
await wait(2500)
console.log('url:', await s.url())
console.log('footer buttons:', JSON.stringify(await s.evaluate(`[...document.querySelectorAll('[data-testid="pane-footer"] button, [data-testid^="action-"]')].map(b => ({testid: b.dataset.testid, text: b.innerText.trim().slice(0,40), disabled: b.disabled || b.getAttribute('aria-disabled') === 'true' || b.hasAttribute('data-disabled')}))`), null, 1))
await s.evaluate(`document.querySelector('[data-testid="action-menu-button"]').click()`)
await wait(800)
console.log('menu items:', JSON.stringify(await s.evaluate(`[...document.querySelectorAll('[role="menuitem"]')].map(b => ({testid: b.dataset.testid, text: b.innerText.trim().slice(0,50), disabled: b.disabled || b.getAttribute('aria-disabled') === 'true' || b.hasAttribute('data-disabled')}))`), null, 1))
await s.shot(`${sp}/explore-menu.png`)
console.log('errors:', s.logs.slice(0, 5))
s.close()
EOF
npx next start -p 3333 > "$SP/next-3333.log" 2>&1 & SERVER=$!
"/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" --headless=new --disable-gpu --hide-scrollbars --no-first-run --remote-debugging-port=9341 --user-data-dir="$SP/chrome-p5" about:blank >/dev/null 2>&1 & CHROME=$!
curl -s -o /dev/null --retry 30 --retry-connrefused --retry-delay 1 http://localhost:3333/ && curl -s -o /dev/null --retry 30 --retry-connrefused --retry-delay 1 http://127.0.0.1:9341/json/version
(cd "$SP" && node explore.mjs 9341 http://localhost:3333 "$SP")
kill $CHROME $SERVER 2>/dev/null; wait $CHROME $SERVER 2>/dev/null; pkill -f "scratchpad/chrome-p5"

Output

Exit code 1
url: /studio/structure/bug;test-bug-life-suspected
footer buttons: [
 {
  "testid": "action-intent-button",
  "text": "",
  "disabled": true
 },
 {
  "text": "",
  "disabled": true
 },
 {
  "text": "",
  "disabled": true
 },
 {
  "testid": "action-publish",
  "text": "Publish",
  "disabled": true
 },
 {
  "testid": "action-menu-button",
  "text": "",
  "disabled": true
 }
]
menu items: [
 {
  "testid": "action-🩹Mark fix merged",
  "text": "🩹 Mark fix merged",
  "disabled": false
 },
 {
  "testid": "action-🪦Declare buried",
  "text": "🪦 Declare buried",
  "disabled": true
 },
 {
  "testid": "action-🧟Report resurrection",
  "text": "🧟 Report resurrection",
  "disabled": true
 },
 {
  "testid": "action-Duplicate",
  "text": "Duplicate",
  "disabled": false
 },
 {
  "testid": "action-Delete",
  "text": "Delete\nCtrl\nOption\nD",
  "disabled": false
 }
]
errors: []

Agent

▸ Read /private/tmp/claude-501/-Users-jashanpreetkaur-Desktop-bug-graveyard/0adab70e...

Input

/private/tmp/claude-501/-Users-jashanpreetkaur-Desktop-bug-graveyard/0adab70e-beca-4347-ad08-acf0d3b85074/scratchpad/explore-menu.png

Output

Agent

▸ Write /private/tmp/claude-501/-Users-jashanpreetkaur-Desktop-bug-graveyard/0adab70e...

Input

/private/tmp/claude-501/-Users-jashanpreetkaur-Desktop-bug-graveyard/0adab70e-beca-4347-ad08-acf0d3b85074/scratchpad/lifecycle-e2e.mjs

Output

File created successfully at: /private/tmp/claude-501/-Users-jashanpreetkaur-Desktop-bug-graveyard/0adab70e-beca-4347-ad08-acf0d3b85074/scratchpad/lifecycle-e2e.mjs (file state is current in your context — no need to Read it back)

Agent

▸ Bash SP=/private/tmp/claude-501/-Users-jashanpreetkaur-Desktop-bug-graveyard/0adab...

Input

$ SP=/private/tmp/claude-501/-Users-jashanpreetkaur-Desktop-bug-graveyard/0adab70e-beca-4347-ad08-acf0d3b85074/scratchpad
npx next start -p 3333 > "$SP/next-3333.log" 2>&1 & SERVER=$!
"/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" --headless=new --disable-gpu --hide-scrollbars --no-first-run --remote-debugging-port=9342 --user-data-dir="$SP/chrome-p5b" about:blank >/dev/null 2>&1 & CHROME=$!
curl -s -o /dev/null --retry 30 --retry-connrefused --retry-delay 1 http://localhost:3333/ && curl -s -o /dev/null --retry 30 --retry-connrefused --retry-delay 1 http://127.0.0.1:9342/json/version
(cd "$SP" && node lifecycle-e2e.mjs 9342 http://localhost:3333) 2>&1 | tee "$SP/e2e.log"
kill $CHROME $SERVER 2>/dev/null; wait $CHROME $SERVER 2>/dev/null; pkill -f "scratchpad/chrome-p5b"; true

Output

1) Suspected dead → Mark fix merged
  ok   only "Mark fix merged" is enabled (✓ 🩹 Mark fix merged | ✗ 🪦 Declare buried | ✗ 🧟 Report resurrection)
  ok   published: status fix-merged, fixMergedAt today (UTC) (1.4s)
  ok   no draft left behind
  FAIL now waiting 7 days to bury, resurrection allowed (✗ 🩹 Mark fix merged | ✗ 🪦 Can bury in 7 days | ✗ 🧟 Report resurrection)
  ok   grave page shows the fix date (0.7s)
2) Fixed 3 days ago
  ok   "Can bury in 4 days", disabled (✗ 🩹 Mark fix merged | ✗ 🪦 Can bury in 4 days | ✓ 🧟 Report resurrection)
3) Fixed 8 days ago → Declare buried
  ok   "Declare buried" is enabled (✗ 🩹 Mark fix merged | ✓ 🪦 Declare buried | ✓ 🧟 Report resurrection)
  ok   published: status buried, buriedAt today (UTC) (1.3s)
  ok   no draft left behind
  ok   grave page shows the burial date (0.7s)
4) Cancelling a resurrection changes nothing
file:///private/tmp/claude-501/-Users-jashanpreetkaur-Desktop-bug-graveyard/0adab70e-beca-4347-ad08-acf0d3b85074/scratchpad/studio-cdp.mjs:46
    throw new Error(`timed out waiting for: ${label}`)
          ^

Error: timed out waiting for: confirm dialog
    at Object.until (file:///private/tmp/claude-501/-Users-jashanpreetkaur-Desktop-bug-graveyard/0adab70e-beca-4347-ad08-acf0d3b85074/scratchpad/studio-cdp.mjs:46:11)
    at async file:///private/tmp/claude-501/-Users-jashanpreetkaur-Desktop-bug-graveyard/0adab70e-beca-4347-ad08-acf0d3b85074/scratchpad/lifecycle-e2e.mjs:111:1

Node.js v24.14.0

Agent

▸ Bash SP=/private/tmp/claude-501/-Users-jashanpreetkaur-Desktop-bug-graveyard/0adab...

Input

$ SP=/private/tmp/claude-501/-Users-jashanpreetkaur-Desktop-bug-graveyard/0adab70e-beca-4347-ad08-acf0d3b85074/scratchpad
cat > "$SP/debug-risen.mjs" <<'EOF'
import {openStudio, wait} from './studio-cdp.mjs'
const [, , port, base] = process.argv
const s = await openStudio(port, base, 'rzjmw6lg')
async function state(label) {
  await s.evaluate(`document.querySelector('[data-testid="action-menu-button"]').click()`)
  await s.until('menu', `document.querySelectorAll('[role="menuitem"]').length > 0`)
  const rect = await s.evaluate(`(() => { const b = [...document.querySelectorAll('[role="menuitem"]')].find(b => b.innerText.includes('resurrection')); const r = b.getBoundingClientRect(); return {x: r.x + r.width / 2, y: r.y + r.height / 2, disabled: b.getAttribute('aria-disabled') ?? String(b.disabled) } })()`)
  await s.send('Input.dispatchMouseEvent', {type: 'mouseMoved', x: rect.x, y: rect.y})
  await wait(900)
  const tip = await s.evaluate(`[...document.querySelectorAll('[data-ui="Popover"], [role="tooltip"], [data-testid*="tooltip"]')].map(e => e.innerText.trim()).filter(Boolean).join(' || ')`)
  console.log(`${label}: disabled=${rect.disabled} tooltip="${tip}"`)
  await s.evaluate(`document.dispatchEvent(new KeyboardEvent('keydown', {key: 'Escape', bubbles: true}))`)
  await wait(300)
}
// "ready" was buried in place during the last run; open it fresh now
await s.navigate('/studio/intent/edit/id=test-bug-life-ready;type=bug')
await s.until('doc', `location.pathname.endsWith('test-bug-life-ready') && !!document.querySelector('[data-testid="action-menu-button"]')`, 60000)
await wait(2000)
await state('fresh load of a buried bug')
for (const t of [3, 8]) { await wait(t * 1000); await state(`after ${t}s more`) }
s.close()
EOF
npx next start -p 3333 > "$SP/next-3333.log" 2>&1 & SERVER=$!
"/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" --headless=new --disable-gpu --hide-scrollbars --no-first-run --remote-debugging-port=9343 --user-data-dir="$SP/chrome-p5c" about:blank >/dev/null 2>&1 & CHROME=$!
curl -s -o /dev/null --retry 30 --retry-connrefused --retry-delay 1 http://localhost:3333/ && curl -s -o /dev/null --retry 30 --retry-connrefused --retry-delay 1 http://127.0.0.1:9343/json/version
(cd "$SP" && node debug-risen.mjs 9343 http://localhost:3333)
kill $CHROME $SERVER 2>/dev/null; wait $CHROME $SERVER 2>/dev/null; pkill -f "scratchpad/chrome-p5c"; true

Output

fresh load of a buried bug: disabled=false tooltip="What's new
Content Agent is generally available"
after 3s more: disabled=false tooltip="What's new
Content Agent is generally available"
after 8s more: disabled=false tooltip="What's new
Content Agent is generally available"

Agent

▸ Bash python3 - <<'EOF' import pathlib p = pathlib.Path('sanity/actions/lifecycle.t...

Input

$ python3 - <<'EOF'
import pathlib
p = pathlib.Path('sanity/actions/lifecycle.tsx')
s = p.read_text()
reps = [
("""  const risen = useRisenZombie(bug?._id)

  function resurrect() {
    setConfirming(false)
    run(async () => {
      if (!bug) return
      const number""",
"""  const risen = useRisenZombie(bug?._id)

  function resurrect() {
    setConfirming(false)
    run(async () => {
      if (!bug) return
      // Checked again here: the live check can lag, or a zombie may just have risen elsewhere.
      const already = await client.fetch<string | null>(RISEN_QUERY, {id: bug._id}, {perspective: 'raw'})
      if (already) throw new Error(`It already rose as “${already}”. Report the next resurrection on that grave.`)
      const number"""),
("""    disabled: busy || Boolean(blocked) || !dead || risen !== null,""",
 """    disabled: busy || Boolean(blocked) || !dead || Boolean(risen),"""),
("""        : risen
          ? `It already rose as “${risen}”. Report the next resurrection on that grave.`
          : risen === undefined
            ? 'Checking whether it has already risen…'
            : 'Creates a zombie of this bug and opens it'),""",
 """        : risen
          ? `It already rose as “${risen}”. Report the next resurrection on that grave.`
          : 'Creates a zombie of this bug and opens it'),"""),
("""// The name of the zombie that already rose from this grave: null if none has,
// undefined while still checking. A grave only rises once; its zombie carries on
// the chain, so the next resurrection is reported on the zombie's grave.
function useRisenZombie(publishedId: string | undefined) {
  const documentStore = useDocumentStore()
  const [risen, setRisen] = useState<string | null | undefined>(undefined)

  useEffect(() => {
    if (!publishedId) return
    const subscription = documentStore
      .listenQuery(
        '*[_type == "bug" && previousLife._ref == $id][0].name',
        {id: publishedId},
        {perspective: 'published'},
      )""",
"""// A grave only rises once: its zombie carries on the chain, so the next
// resurrection is reported on the zombie's grave.
const RISEN_QUERY = '*[_type == "bug" && previousLife._ref == $id][0].name'

// The name of the zombie that already rose from this grave, kept up to date;
// null if none has (or while the first check is still running).
function useRisenZombie(publishedId: string | undefined) {
  const documentStore = useDocumentStore()
  const [risen, setRisen] = useState<string | null>(null)

  useEffect(() => {
    if (!publishedId) return
    const subscription = documentStore
      .listenQuery(RISEN_QUERY, {id: publishedId}, {perspective: 'published'})"""),
]
for a, b in reps:
    assert a in s, a[:80]
    s = s.replace(a, b)
p.write_text(s)
print("patched")
EOF
npx tsc --noEmit && echo "tsc ok"; npm run lint --silent && echo "lint ok"

Output

patched
tsc ok
lint ok

Agent

▸ Bash SP=/private/tmp/claude-501/-Users-jashanpreetkaur-Desktop-bug-graveyard/0adab...

Input

$ SP=/private/tmp/claude-501/-Users-jashanpreetkaur-Desktop-bug-graveyard/0adab70e-beca-4347-ad08-acf0d3b85074/scratchpad
python3 - "$SP/lifecycle-e2e.mjs" <<'EOF'
import sys, pathlib
p = pathlib.Path(sys.argv[1]); s = p.read_text()
a = """await open('test-bug-life-buried')
items = await menu()
check('the old grave cannot rise twice', items.find((i) => i.text.includes('resurrection'))?.disabled === true, describe(items))"""
b = """await open('test-bug-life-buried')
await pollUntil('the old grave cannot rise twice', async () => {
  const items = await menu()
  return items.find((i) => i.text.includes('resurrection'))?.disabled === true || describe(items)
}, 15000)"""
assert a in s
p.write_text(s.replace(a, b))
EOF
echo "zombies of test bugs before reset: $(npx sanity documents query --api-version 2026-09-28 'count(*[_type == "bug" && previousLife._ref in ["test-bug-life-suspected","test-bug-life-waiting","test-bug-life-ready","test-bug-life-buried","test-bug-life-drafted"]])' 2>&1 | grep -v 'npm warn' | tail -1)"
npx sanity documents create "$SP/life-docs.json" --replace 2>&1 | grep -v "npm warn" | head -1
npm run build 2>&1 | grep -E "Compiled|rror"
npx next start -p 3333 > "$SP/next-3333.log" 2>&1 & SERVER=$!
"/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" --headless=new --disable-gpu --hide-scrollbars --no-first-run --remote-debugging-port=9344 --user-data-dir="$SP/chrome-p5d" about:blank >/dev/null 2>&1 & CHROME=$!
curl -s -o /dev/null --retry 30 --retry-connrefused --retry-delay 1 http://localhost:3333/ && curl -s -o /dev/null --retry 30 --retry-connrefused --retry-delay 1 http://127.0.0.1:9344/json/version
(cd "$SP" && node lifecycle-e2e.mjs 9344 http://localhost:3333) 2>&1 | tee "$SP/e2e.log"
kill $CHROME $SERVER 2>/dev/null; wait $CHROME $SERVER 2>/dev/null; pkill -f "scratchpad/chrome-p5d"; true

Output

zombies of test bugs before reset:  ›   test-bug-life-buried","test-bug-life-drafted"]])
Upserted:
✓ Compiled successfully in 799ms
1) Suspected dead → Mark fix merged
  ok   only "Mark fix merged" is enabled (✓ 🩹 Mark fix merged | ✗ 🪦 Declare buried | ✗ 🧟 Report resurrection)
  ok   published: status fix-merged, fixMergedAt today (UTC) (1.3s)
  ok   no draft left behind
  ok   now waiting 7 days to bury, resurrection allowed (✗ 🩹 Mark fix merged | ✗ 🪦 Can bury in 7 days | ✓ 🧟 Report resurrection)
  ok   grave page shows the fix date (0.9s)
2) Fixed 3 days ago
  ok   "Can bury in 4 days", disabled (✗ 🩹 Mark fix merged | ✗ 🪦 Can bury in 4 days | ✓ 🧟 Report resurrection)
3) Fixed 8 days ago → Declare buried
  ok   "Declare buried" is enabled (✗ 🩹 Mark fix merged | ✓ 🪦 Declare buried | ✓ 🧟 Report resurrection)
  ok   published: status buried, buriedAt today (UTC) (1.5s)
  ok   no draft left behind
  ok   grave page shows the burial date (0.7s)
4) Cancelling a resurrection changes nothing
  ok   confirm dialog shows the message
  ok   clicked Cancel
  ok   no zombie was created
5) Unpublished edits block the actions
  ok   all three disabled (✗ 🩹 Mark fix merged | ✗ 🪦 Declare buried | ✗ 🧟 Report resurrection)
6) Buried → Report resurrection → Zombie #1
file:///private/tmp/claude-501/-Users-jashanpreetkaur-Desktop-bug-graveyard/0adab70e-beca-4347-ad08-acf0d3b85074/scratchpad/studio-cdp.mjs:46
    throw new Error(`timed out waiting for: ${label}`)
          ^

Error: timed out waiting for: document test-bug-life-buried
    at Object.until (file:///private/tmp/claude-501/-Users-jashanpreetkaur-Desktop-bug-graveyard/0adab70e-beca-4347-ad08-acf0d3b85074/scratchpad/studio-cdp.mjs:46:11)
    at async open (file:///private/tmp/claude-501/-Users-jashanpreetkaur-Desktop-bug-graveyard/0adab70e-beca-4347-ad08-acf0d3b85074/scratchpad/lifecycle-e2e.mjs:53:3)
    at async file:///private/tmp/claude-501/-Users-jashanpreetkaur-Desktop-bug-graveyard/0adab70e-beca-4347-ad08-acf0d3b85074/scratchpad/lifecycle-e2e.mjs:127:1

Node.js v24.14.0

Agent

▸ Bash SP=/private/tmp/claude-501/-Users-jashanpreetkaur-Desktop-bug-graveyard/0adab...

Input

$ SP=/private/tmp/claude-501/-Users-jashanpreetkaur-Desktop-bug-graveyard/0adab70e-beca-4347-ad08-acf0d3b85074/scratchpad
python3 - "$SP/lifecycle-e2e.mjs" <<'EOF'
import sys, pathlib
p = pathlib.Path(sys.argv[1]); s = p.read_text()
a = "await graveTab.evaluate('window.__noReload = true')\nawait open('test-bug-life-buried')"
b = "await graveTab.evaluate('window.__noReload = true')\nawait studio.send('Page.bringToFront') // background tabs are throttled\nawait open('test-bug-life-buried')"
assert a in s
p.write_text(s.replace(a, b))
EOF
npx sanity documents create "$SP/life-docs.json" --replace 2>&1 | grep -v "npm warn" | head -1
npx next start -p 3333 > "$SP/next-3333.log" 2>&1 & SERVER=$!
"/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" --headless=new --disable-gpu --hide-scrollbars --no-first-run --remote-debugging-port=9345 --user-data-dir="$SP/chrome-p5e" about:blank >/dev/null 2>&1 & CHROME=$!
curl -s -o /dev/null --retry 30 --retry-connrefused --retry-delay 1 http://localhost:3333/ && curl -s -o /dev/null --retry 30 --retry-connrefused --retry-delay 1 http://127.0.0.1:9345/json/version
(cd "$SP" && node lifecycle-e2e.mjs 9345 http://localhost:3333) 2>&1 | tee "$SP/e2e.log"
kill $CHROME $SERVER 2>/dev/null; wait $CHROME $SERVER 2>/dev/null; pkill -f "scratchpad/chrome-p5e"; true

Output

Upserted:
1) Suspected dead → Mark fix merged
  ok   only "Mark fix merged" is enabled (✓ 🩹 Mark fix merged | ✗ 🪦 Declare buried | ✗ 🧟 Report resurrection)
  ok   published: status fix-merged, fixMergedAt today (UTC) (1.4s)
  ok   no draft left behind
  ok   now waiting 7 days to bury, resurrection allowed (✗ 🩹 Mark fix merged | ✗ 🪦 Can bury in 7 days | ✓ 🧟 Report resurrection)
  ok   grave page shows the fix date (1.2s)
2) Fixed 3 days ago
  ok   "Can bury in 4 days", disabled (✗ 🩹 Mark fix merged | ✗ 🪦 Can bury in 4 days | ✓ 🧟 Report resurrection)
3) Fixed 8 days ago → Declare buried
  ok   "Declare buried" is enabled (✗ 🩹 Mark fix merged | ✓ 🪦 Declare buried | ✓ 🧟 Report resurrection)
  ok   published: status buried, buriedAt today (UTC) (1.5s)
  ok   no draft left behind
  ok   grave page shows the burial date (1.1s)
4) Cancelling a resurrection changes nothing
  ok   confirm dialog shows the message
  ok   clicked Cancel
  ok   no zombie was created
5) Unpublished edits block the actions
  ok   all three disabled (✗ 🩹 Mark fix merged | ✗ 🪦 Declare buried | ✗ 🧟 Report resurrection)
6) Buried → Report resurrection → Zombie #1
  ok   clicked "Let it rise"
  ok   Studio opened the new zombie (c3812e41-4f19-495e-8011-60a6158d9802)
  ok   name "(Zombie #1)" (Lifecycle test: buried (Zombie #1))
  ok   status zombie, born today, timesResurrected 1 ({"s":"zombie","b":"2026-09-28","t":1})
  ok   previousLife → the buried bug
  ok   same language and cause, no epitaph yet
  ok   unique slug (lifecycle-test-buried-zombie-1)
  ok   zombie is published, with no draft
  ok   open grave tab shows "Risen from this grave" without reloading (1.4s)
  ok   homepage lists the zombie (0.2s)
  ok   the old grave cannot rise twice (0.3s)
7) Zombie #1 → Mark fix merged → Report resurrection → Zombie #2
  ok   a walking zombie can have its fix merged (✓ 🩹 Mark fix merged | ✗ 🪦 Declare buried | ✗ 🧟 Report resurrection)
  ok   zombie #1 is fix-merged today (1.8s)
  ok   name "(Zombie #2)", not "(Zombie #1) (Zombie #2)" (Lifecycle test: buried (Zombie #2))
  ok   timesResurrected 2, previousLife → zombie #1
  ok   zombie #2 page shows both past lives, oldest first (0.5s)
8) No stray drafts anywhere
  ok   only the draft we made on purpose exists (["drafts.test-bug-life-drafted"])
  ok   no errors in the Studio
ZOMBIES=a6b031eb-78c1-4104-a5af-8565629d2597,c3812e41-4f19-495e-8011-60a6158d9802
all checks passed

Agent

▸ Bash npx sanity documents delete a6b031eb-78c1-4104-a5af-8565629d2597 2>&1 | grep ...

Input

$ npx sanity documents delete a6b031eb-78c1-4104-a5af-8565629d2597 2>&1 | grep -v "npm warn" | tail -1; npx sanity documents delete c3812e41-4f19-495e-8011-60a6158d9802 2>&1 | grep -v "npm warn" | tail -1; npx sanity documents delete test-bug-life-suspected test-bug-life-waiting test-bug-life-ready test-bug-life-buried test-bug-life-drafted drafts.test-bug-life-drafted 2>&1 | grep -v "npm warn" | tail -1
echo "left over: $(npx --yes sanity@latest documents query --api-version 2026-09-28 '*[_type == "bug" && (name match "Lifecycle test*" || string::startsWith(_id, "test-bug-life") || string::startsWith(_id, "drafts.test-bug-life"))]._id' 2>/dev/null | tr -d ' \n')"; echo "bugs now: $(npx --yes sanity@latest documents query --api-version 2026-09-28 '*[_type == "bug" && !(_id in path("drafts.**"))].name' 2>/dev/null | tr -d '\n' | sed 's/  */ /g')"

Output

Deleted 1 document
Deleted 1 document
Deleted 6 documents
left over: []
bugs now: [ "NullPointerException in checkout", "Timezone bug in scheduler", "Timezone bug in scheduler (Zombie #1)"]

Agent

Everything is cleaned up, and the dataset is back to your 3 bugs. Next: the final build, lint and type-check.

Agent

▸ Bash npx tsc --noEmit && echo "tsc ok"; npm run lint --silent && echo "lint ok"; n...

Input

$ npx tsc --noEmit && echo "tsc ok"; npm run lint --silent && echo "lint ok"; npx sanity schemas validate 2>&1 | grep -E "Errors|Warnings"; npm run build 2>&1 | grep -E "Compiled|TypeScript|rror"; git status --short

Output

tsc ok
lint ok
✖ Errors:   0 errors
⚠ Warnings: 0 warnings
✓ Compiled successfully in 698ms
  Running TypeScript ...
  Finished TypeScript in 923ms ...
 M sanity.config.ts
?? sanity/actions/
?? sanity/lib/lifecycle.ts

Agent

All clean: type-check, lint, 0 schema errors and 0 warnings, and a passing build. I'll commit the code, deploy it to Vercel, and check the live Studio before writing the NOTES entry.

Agent

▸ Bash git add sanity.config.ts sanity/actions sanity/lib/lifecycle.ts && git commit...

Input

$ git add sanity.config.ts sanity/actions sanity/lib/lifecycle.ts && git commit -q -F - <<'EOF'
Add lifecycle document actions to the Studio

Bugs get three actions after Publish: "Mark fix merged" (from suspected
dead or zombie, sets fixMergedAt), "Declare buried" (once the fix has
held for BURIAL_WAIT_DAYS = 7 days, sets buriedAt; otherwise shows
"Can bury in N days"), and "Report resurrection" (after a confirm
dialog, creates a published zombie with previousLife, timesResurrected
+ 1 and a unique slug, then opens it). Zombies go through the same
cycle, so zombies of zombies work.

The actions patch the published document directly, guarded by its
revision, so they never leave drafts, and they are disabled while
unpublished edits exist. A grave rises only once. Dates are UTC.

Co-Authored-By: Claude Opus 5.5 <[e-mail]>
EOF
git log --oneline | head -1
npx vercel@60 deploy --prod --yes 2>&1 | grep -E "Production:|Aliased|Error|error|READY|https://bug-graveyard" | grep -v "vercel curl\|vercel inspect" | head -6

Output

4352c77 Add lifecycle document actions to the Studio
  Production      https://bug-graveyard-ab38mxs28-jashanpreet-kaur.vercel.app
[2K[1A[2K[G  Production      https://bug-graveyard-ab38mxs28-jashanpreet-kaur.vercel.app
▲ Aliased         https://bug-graveyard.vercel.app
    "url": "https://bug-graveyard-ab38mxs28-jashanpreet-kaur.vercel.app",
    "readyState": "READY",

Agent

It's deployed and aliased to https://bug-graveyard.vercel.app. Next is a read-only check of the live Studio: it opens your three real bugs and reads their action menus without clicking anything.

Agent

▸ Bash SP=/private/tmp/claude-501/-Users-jashanpreetkaur-Desktop-bug-graveyard/0adab...

Input

$ SP=/private/tmp/claude-501/-Users-jashanpreetkaur-Desktop-bug-graveyard/0adab70e-beca-4347-ad08-acf0d3b85074/scratchpad
cat > "$SP/live-menus.mjs" <<'EOF'
// Read-only: opens real bugs in the live Studio and reads their lifecycle menus. Clicks nothing.
import {openStudio, wait} from './studio-cdp.mjs'
const [, , port, base] = process.argv
const s = await openStudio(port, base, 'rzjmw6lg')
let failures = 0
async function menu() {
  await s.evaluate(`document.querySelector('[data-testid="action-menu-button"]').click()`)
  await s.until('menu', `document.querySelectorAll('[role="menuitem"]').length > 0`)
  const items = await s.evaluate(`[...document.querySelectorAll('[role="menuitem"]')].filter(b => /fix merged|bur|resurrection/i.test(b.innerText)).map(b => (b.getAttribute('aria-disabled') === 'true' || b.disabled || b.hasAttribute('data-disabled') ? '✗ ' : '✓ ') + b.innerText.trim()).join(' | ')`)
  await s.evaluate(`document.dispatchEvent(new KeyboardEvent('keydown', {key: 'Escape', bubbles: true}))`)
  await wait(300)
  return items
}
for (const [id, want] of [
  ['test-bug-timezone-scheduler-zombie-1', '✓ 🩹 Mark fix merged | ✗ 🪦 Declare buried | ✗ 🧟 Report resurrection'],
  ['test-bug-timezone-scheduler', '✗ 🩹 Mark fix merged | ✗ 🪦 Declare buried | ✗ 🧟 Report resurrection'],
  ['test-bug-nullpointer-checkout', '✗ 🩹 Mark fix merged | ✗ 🪦 Declare buried | ✓ 🧟 Report resurrection'],
]) {
  await s.navigate(`/studio/intent/edit/id=${id};type=bug`)
  await s.until(id, `location.pathname.endsWith(${JSON.stringify(id)}) && !!document.querySelector('[data-testid="action-menu-button"]')`, 60000)
  let got
  for (let i = 0; i < 10 && got !== want; i++) { await wait(1000); got = await menu() }
  if (got !== want) failures++
  console.log(`  ${got === want ? 'ok  ' : 'FAIL'} ${id}: ${got}`)
}
console.log('  studio errors:', s.logs.length ? s.logs.slice(0, 2) : 'none')
console.log(failures ? `${failures} FAILED` : 'live Studio has the actions')
s.close()
EOF
"/Applications/Google Chrome.app/Contents/MacOS/Google Chrome" --headless=new --disable-gpu --hide-scrollbars --no-first-run --remote-debugging-port=9346 --user-data-dir="$SP/chrome-live5" about:blank >/dev/null 2>&1 & CHROME=$!
curl -s -o /dev/null --retry 30 --retry-connrefused --retry-delay 1 http://127.0.0.1:9346/json/version
(cd "$SP" && node live-menus.mjs 9346 https://bug-graveyard.vercel.app)
kill $CHROME 2>/dev/null; wait $CHROME 2>/dev/null; pkill -f "scratchpad/chrome-live5"
for p in / /grave/timezone-bug-in-scheduler; do printf "  live %-34s %s\n" "$p" "$(curl -s -o /dev/null -w '%{http_code}' https://bug-graveyard.vercel.app$p)"; done

Output

ok   test-bug-timezone-scheduler-zombie-1: ✓ 🩹 Mark fix merged | ✗ 🪦 Declare buried | ✗ 🧟 Report resurrection
  ok   test-bug-timezone-scheduler: ✗ 🩹 Mark fix merged | ✗ 🪦 Declare buried | ✗ 🧟 Report resurrection
  ok   test-bug-nullpointer-checkout: ✗ 🩹 Mark fix merged | ✗ 🪦 Declare buried | ✓ 🧟 Report resurrection
  studio errors: none
live Studio has the actions
  live /                                  200
  live /grave/timezone-bug-in-scheduler   200

Agent

▸ Bash tail -2 NOTES.md && cat >> NOTES.md <<'EOF' --- ## Phase 5: Lifecycle docum...

Input

$ tail -2 NOTES.md && cat >> NOTES.md <<'EOF'

---

## Phase 5: Lifecycle document actions (2026-09-29)

### What I asked for

- Three custom Studio actions on bugs, registered through `document.actions` in
  `sanity.config.ts`, keeping Sanity's own Publish, Delete and so on:
  - **🩹 Mark fix merged**, enabled for suspected-dead bugs: status becomes fix-merged,
    `fixMergedAt` becomes today, and the change is published.
  - **🪦 Declare buried**, enabled once a fix has held for 7 days; otherwise the label
    says how long is left ("Can bury in 4 days"). Status becomes buried, `buriedAt`
    becomes today, and the change is published.
  - **🧟 Report resurrection**, for fix-merged or buried bugs. After a confirm dialog
    ("Are you sure? This bug will rise from its grave.") it creates a new zombie bug:
    `previousLife` points at this bug, `timesResurrected` goes up by one, the name
    becomes "<name> (Zombie #n)", with the same language and cause, a unique slug and
    today as `bornAt`. Then it opens the zombie so I can write its epitaph.
- UTC dates. Drafts handled properly: act on the published document and leave no
  stray drafts. Zombies go through the same lifecycle, so zombies of zombies work. The
  7-day rule in a single constant.
- Test it end to end with temporary bugs, check that the site updates live, run build,
  lint and type-check, add this entry, commit and deploy. Explain document actions for
  the write-up.

### What was built

- `sanity/actions/lifecycle.tsx`: the three actions
- `sanity/lib/lifecycle.ts`: `BURIAL_WAIT_DAYS = 7` and small helpers: `todayUTC`,
  `daysBetween`, `daysUntilBurial`, `zombieName`, `slugify`. It doesn't import
  `sanity`, so the site could use it too.
- `sanity.config.ts`: `document.actions` adds the three actions right after Publish,
  for bugs only

**Decisions that go beyond the brief:**
- **"Mark fix merged" also works on a walking zombie.** Without that, a zombie could
  never start its own lifecycle.
- **The actions write straight to the published document,** in one change guarded by
  its revision (`ifRevisionId`). There is no draft step, so nothing gets left behind.
  They are disabled while the bug has unpublished edits ("Publish or discard your
  changes first"), because that draft would later overwrite the new status.
- **The zombie is created already published,** so it appears on the site straight
  away, then opens in the Studio. Writing its epitaph is then an ordinary edit and
  publish.
- **A grave only rises once.** "Report resurrection" is disabled on a grave a zombie
  already came from ("It already rose as …"), and this is checked again at the moment
  of confirming. The next resurrection belongs on the zombie's own grave, which keeps
  every chain a single line.
- **The zombie copies the language and cause of death, but not the severity.** Its
  slug gets `-2`, `-3` and so on if the name is already taken.

**End-to-end test:** a production build, with headless Chrome clicking the real Studio
buttons. Five temporary bugs covered every situation, and **all 34 checks passed**:
- **Enabled/disabled states** in each status, including "🪦 Can bury in 7 days" right
  after a fix and "Can bury in 4 days" for a fix 3 days old.
- **Mark fix merged and Declare buried** wrote today's UTC date, and no drafts were
  left behind.
- **Cancel in the confirm dialog** created nothing.
- **Unpublished edits** disabled all three actions.
- **Resurrecting a buried bug** created "(Zombie #1)" with the correct fields and a
  unique slug, and opened it in the Studio.
- **A grave tab that was already open** showed "Risen from this grave" 1.4s later,
  without reloading.
- **The old grave could not rise twice.**
- **A zombie of a zombie** was named "(Zombie #2)", not "(Zombie #1) (Zombie #2)", and
  its page lists both past lives, oldest first.

Every temporary document was deleted afterwards. After the deploy, a read-only check of
the live Studio showed the right menu for each of the three real bugs.

### What went wrong and how we fixed it

- **"Report resurrection" stayed disabled right after another action.** My first
  version disabled it while it was still checking whether the grave had already
  risen. Sanity re-creates the action component whenever the document changes, so
  each change restarted that check, and the button was disabled for a second or two.
  The test clicked during that window, and the confirm dialog never opened. Fix: don't
  block while checking. The button is only disabled once a zombie is known to exist,
  and the final check happens when you confirm.
- **Test script problem, not an app bug:** headless Chrome slows down tabs in the
  background, so the Studio stalled after the test opened a second tab.
  `Page.bringToFront` fixed it.
- **Signing the headless Studio in:** the Studio keeps its token in `localStorage`
  under `__studio_auth_token_<projectId>`. The test put my CLI login token there
  before the page loaded, in a throwaway Chrome profile, and never printed it.
- **Still open: backfilling old bugs.** `fixMergedAt`, `buriedAt` and
  `timesResurrected` are read-only in the Studio, and the actions always use today. So
  a bug fixed months ago can't be given its real dates by hand; only a script or the
  API can do that.

### Sanity notes for the write-up

**How document actions work, in plain words:**
- The buttons at the bottom of a document in Sanity Studio (Publish, Duplicate, Delete,
  and so on) are all *document actions*, and you can add your own.
- **An action is a small React component.** Sanity renders it for the open document
  and gives it the document's current state: the published version, any unpublished
  draft, its ID and type. It returns a description of a button: a label, whether it's
  disabled, a tooltip, what happens on click, and optionally a dialog such as a
  confirm box.
- **It updates itself.** Because it's a component, Sanity re-renders it whenever the
  document changes. That's how "Can bury in 4 days" and the enabled/disabled states
  stay correct without any refresh logic.
- **It can use the Studio's hooks:** `useClient` to write data, `useRouter` to open
  another document, and `useDocumentStore().listenQuery` for a live GROQ subscription.
- **It runs as the signed-in person.** The action runs in the browser with that
  person's Sanity permissions, so there's no API token in the code.
- **You register actions in `sanity.config.ts`.** `document.actions` is a function
  that receives Sanity's default list plus some context (which type of document, and
  so on) and returns the list to show. The first one becomes the big button; the rest
  go in the "…" menu. Here the lifecycle actions go right after Publish, and only for
  bugs.

**Other things worth mentioning:**
- **Actions can own read-only fields.** Marking fields `readOnly` stops people editing
  them by hand while code can still set them. That turns the dates and the
  resurrection counter into a record of what actually happened.
- **Drafts are separate documents.** Editing creates a `drafts.<id>` copy, and
  publishing copies it over the real one. These actions skip that step and change the
  published document directly, with `ifRevisionId` (the write fails if someone else
  changed the bug first).
- **The built-in dialogs are declarative:** `dialog: {type: 'confirm', message,
  onConfirm, onCancel}`, and `navigateIntent('edit', {id, type})` opens a document.
- **The whole lifecycle runs on the same live pipeline as the site.** Clicking an
  action updates the homepage and grave pages within about a second, through the
  Studio's `<SanityLive />` and the webhook.
EOF
git add NOTES.md && git commit -q -m "Add the Phase 5 notes

Co-Authored-By: Claude Opus 5.5 <[e-mail]>" && GIT_TERMINAL_PROMPT=0 git push 2>&1 | tail -1; git log --oneline | head -2; git status --short | wc -l | xargs echo "uncommitted files:"

Output

- **Which Sanity CLI runs matters.** `npx sanity` is the project's CLI (v5), and
  `npx sanity@latest` is the newest (v8), which adds `api`, `organizations` and more.
   afae328..f638d72  main -> main
f638d72 Add the Phase 5 notes
4352c77 Add lifecycle document actions to the Studio
uncommitted files: 0

Agent

The lifecycle actions are live in the Studio at https://bug-graveyard.vercel.app/studio (open a bug, then the "…" menu next to Publish). They're committed (4352c77, notes in f638d72), pushed and deployed. Type-check, lint, schema validation and the build all pass.

What's there: sanity/actions/lifecycle.tsx holds the three actions, and sanity/lib/lifecycle.ts holds BURIAL_WAIT_DAYS = 7 plus the date helpers. sanity.config.ts adds the actions right after Publish, for bugs only. Dates are UTC, so at 02:00 in India they record the previous day.

Decisions that go beyond your brief:
- "Mark fix merged" also works on a walking zombie. Otherwise a zombie could never start its own lifecycle.
- The actions change the published bug directly, in a single change that fails if someone else edited the bug first. No draft is ever created. They're disabled while you have unpublished edits, because your draft would later overwrite the new status.
- The new zombie is created already published, so it shows on the site straight away, then opens for you to write its epitaph.
- A grave only rises once. A second resurrection belongs on the zombie's grave, which keeps each chain a single line.

How I tested it: a script clicked the real Studio buttons against a production build, using five temporary bugs, and all 34 checks passed. They cover:
- every enabled/disabled state, including "🪦 Can bury in 4 days";
- today's UTC dates, with no drafts left behind;
- cancelling the confirm dialog;
- being blocked by unpublished edits;
- zombies of zombies (named "(Zombie #2)");
- the site updating within about 1.5 seconds, including an already open grave page.

The test bugs are deleted. After deploying, a read-only check confirmed the live Studio shows the right menu for your 3 real bugs.

A bug the test caught: right after one action changed a bug, "Report resurrection" was briefly disabled. My check for "has this grave already risen?" restarted after every change and blocked the button while running. It now only disables once a zombie is known to exist, and checks again when you confirm.

Still open: the dates and resurrection count are read-only and the actions always use today. So an old bug can't be given its real historical dates in the Studio; only a script or the API can do that.

Be careful trying it: these actions change your real data. "Report resurrection" on "NullPointerException in checkout" will create a real zombie.

For your write-up: how document actions work
- Every button at the bottom of a Sanity document (Publish, Duplicate, Delete) is a document action, and you can add your own.
- An action is a small React component. Sanity gives it the document's current state (the published version and any unpublished draft), and it describes a button: label, disabled or not, tooltip, what happens on click, and optionally a confirm dialog.
- Because it's a component, it updates whenever the document changes. That keeps labels like "Can bury in 4 days" current with no extra code.
- It runs in the browser as the signed-in person, using their permissions, so there's no API token in the code.
- You register actions in sanity.config.ts with document.actions. That function receives Sanity's default list and returns the list to show. The first one becomes the big button, and the rest go in the "…" menu.

There's a longer version of this in the Phase 5 entry of NOTES.md.

Show more

41 messages (range 358-398) of 719 total

What I learned

• Document actions go a long way. They're just React components that re-render with the document, so a live countdown like "Can bury in 4 days" needs no refresh logic. And they run as the signed-in editor, so there's no token in the code.
• Test against a production build from day one. npm run dev hid both live-update bugs. I'd also connect Vercel to GitHub at the start: I only added the login connection near the end, so most deploys were a manual vercel deploy --prod.
• The App SDK reuses the Studio's ideas outside the Studio. Handles, projections and document actions, all live, in a plain React app. Sharing one rules file kept the Studio and the Morgue from drifting apart.
• Workflows can model this lifecycle, and the in-memory test engine makes a rule like "7 days" easy to test by moving the clock. But a real integration needs Studio 6 and a runtime, so for now it stays an experiment.
• Directing an agent works best in small phases, each with a clear brief, a test and a build-log entry. That log is also what this post was fact-checked against.

Thanks for reading. May your bugs rest in peace. 🪦