feat(blog): add draft/published lifecycle to blog posts

[aka-sacci-ccr]

What is this Contribution About?

Adds a draft/published lifecycle to the blog/ app.

The status vocabulary comes from #1603 — draft | published | archived | generating | awaiting_review, exported as PostStatus alongside isPublishedStatus, under the same names and in the same file (blog/types.ts) as that PR, so whichever lands second is a near-trivial merge. generating and awaiting_review are what the autonomous-blog agent writes while a post is still being produced.

Absent means published. Every post on every site running this app today has no status field, so isPublishedStatus returns true for an absent value — and for "", which is what an unset CMS field serializes to. Requiring an explicit "published" would empty every blog in production on the version bump.

Everything else is an allowlist. Only absent and "published" are live; any other value, including one this app doesn't recognize yet, is kept out of listings. With a defined CMS vocabulary that's the safe direction: shipping a half-generated post is worse than hiding one.

Lists exclude unpublished posts. Done in filterRoutablePosts, already the choke point for "should this post be reachable". All three list loaders (BlogpostList, BlogRelatedPosts, BlogpostListing) inherit it through filterPosts → handlePosts; none of them changed.

Detail loaders keep serving unpublished posts, unindexable. BlogPostPage and BlogPostItem do not hide them — serving the page is how the CMS previews unpublished work. They force seo.noIndexing = true instead, using the existing Seo.noIndexing field. Any seo the post already carries is preserved; only noIndexing is overridden.

Files

File	Change
blog/types.ts	status?: PostStatus on BlogPost; PostStatus + isPublishedStatus
blog/core/handlePosts.ts	filterRoutablePosts drops unpublished posts
blog/loaders/BlogPostPage.ts	noIndexing: post?.seo?.noIndexing || !isPublishedStatus(post.status)
blog/loaders/BlogPostItem.ts	returns { ...post, seo: { ...post.seo, noIndexing: true } } when unpublished
blog/tests/	new; see below

Relationship to #1603

#1603 (feat/autonomous-blog-compatibility) carries the same status feature bundled with the shoppable product blocks. It's had CHANGES_REQUESTED since 14 Jul, so this PR splits the status half out to land on its own. Two deliberate differences, both open to being switched to that PR's approach if reviewers prefer it:

• Choke point. feat(blog): shoppable product blocks + hide non-published posts #1603 filters inside getRecordsByPath, which hides unpublished posts from every loader including the single-post page, then re-admits them via an includeUnpublished flag. This filters in filterRoutablePosts, which is list-only, so the detail loaders never need the opt-in.
• Preview. Because of the above, feat(blog): shoppable product blocks + hide non-published posts #1603 needs ?preview=true on the single-post URL to show a draft — which only works once Studio appends it. Here the single-post page always renders, so CMS preview works before any Studio change ships.

The PostStatus / isPublishedStatus definitions are deliberately identical to #1603's, so the overlap is confined to those two behavioural choices.

Verification

• grep for a status prop on blog records: the only hits are Review/submitReview's unrelated "Review status" comments. No record type already carried a status, so no site's existing string gets reinterpreted here.
• filterRoutablePosts callers: exactly one — filterPosts. Nothing else in the repo imports it, so the choke point holds.
• Ran the deco bundler locally (deno run -A --no-lock jsr:@deco/deco/scripts/bundle) and confirmed no manifest changes — the earlier CI failure was a test file sitting in blog/loaders/, which the bundler registers as a block. Tests now live in blog/tests/, which isn't a block directory.

Tests

The repo had no Deno.test anywhere, so there was no existing tier to match; these use plain Deno.test + @std/assert (already in the import map).

• blog/tests/handlePosts.test.ts — absent status appears (the upgrade-safety case), "" appears, "published" appears, each of the four non-published statuses is dropped, an unrecognized string is dropped, and slug-less records are still dropped alongside unpublished ones.
• blog/tests/blogPostDetail.test.ts — both detail loaders against a stubbed ctx.get: every non-published status is still returned with seo.noIndexing true, a draft that already has an seo object keeps its other fields, and a published post is left indexable and untouched.

13 tests pass. deno task check (fmt + lint + deno check **/mod.ts) is clean — it runs as the pre-commit hook.

Rollout

This reaches a site only after an apps release plus a version bump in that site — not on a Studio deploy. The editor UI (decocms/studio#4302) and the spire-agent migration that writes post.status ship separately.

Issue Link

• Issue: n/a

Loom Video

n/a — no visual change; behaviour is covered by the tests above.

Demonstration Link

Branch: blog-draft-published-status

🤖 Generated with Claude Code

[github-actions]

Tagging Options

Should a new tag be published when this PR is merged?

• 👍 for Patch 0.161.1 update
• 🎉 for Minor 0.162.0 update
• 🚀 for Major 1.0.0 update

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 10a23b47-4bed-41fc-a77d-36369fd78ecc

📥 Commits

Reviewing files that changed from the base of the PR and between 3670ea3 and 5bbe17b.

📒 Files selected for processing (6)

• blog/core/handlePosts.test.ts
• blog/core/handlePosts.ts
• blog/loaders/BlogPostItem.ts
• blog/loaders/BlogPostPage.ts
• blog/loaders/blogPostDetail.test.ts
• blog/types.ts

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The PR adds optional draft status to BlogPost, excludes drafts from post routing, and marks drafts as non-indexable in BlogPostItem and BlogPostPageLoader. Tests cover routing, draft handling, SEO preservation, published posts, and missing posts.

Changes

Draft blog post handling

Layer / File(s)	Summary
Status contract and routing filter blog/types.ts, blog/core/handlePosts.ts, blog/core/handlePosts.test.ts	BlogPost accepts optional "draft" and "published" statuses. Only "draft" is treated as a draft. Draft and malformed posts are excluded from routing.
Detail loader draft handling blog/loaders/BlogPostItem.ts, blog/loaders/BlogPostPage.ts, blog/loaders/blogPostDetail.test.ts	Draft detail responses set seo.noIndexing to true while preserving other SEO fields. Missing posts return null. Tests cover draft and published behavior.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Merge Risk: 🔵 Low · up to 5bbe1

Draft posts remain directly servable for CMS preview and are marked noindex; consuming routes should ensure drafts require preview authorization so unpublished content is not exposed publicly. This is a bounded follow-up risk and the PR is otherwise mergeable with explicit owner awareness.

Sequence Diagram(s)

sequenceDiagram
  participant Request
  participant BlogPostItem
  participant AppContext
  participant BlogPost
  Request->>BlogPostItem: Request post by slug
  BlogPostItem->>AppContext: Get blog post collection
  AppContext->>BlogPost: Resolve matching post
  BlogPost-->>BlogPostItem: Return post or no match
  BlogPostItem-->>Request: Return post with draft noIndexing or null

Loading

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly summarizes the main change: adding draft and published lifecycle support to blog posts.
Description check	✅ Passed	The description explains the behavior, implementation, tests, verification, rollout, and demonstration branch; the issue link is marked n/a.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch blog-draft-published-status

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[cubic-dev-ai]

No issues found across 6 files

_{Re-trigger cubic}