[jordesign]

Summary

• Document the spacefast:document JSON header used by source-backed WordPress documents.
• Explain required fields, UTC publication dates, editor round trips, and what happens when the header is absent.
• State explicitly that YAML front matter does not set WordPress titles or dates, and show the supported migration format.
• Add navigation, related-guide links, and built-route coverage.

This documents existing behavior. It does not add YAML front-matter support or change source synchronization.

Validation

• Parsed and canonicalized the documented Markdown example with the actual document-metadata parser.
• check, validate, build, audit, verify:public-safety, and verify:routes pass.
• verify:prose passes with CI-pinned Vale 3.17.1.
• 14 corpus, LLM-index, and composition-audit tests pass.
• git diff --check passes.

Tag @indent to continue the conversation here.

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}

[indent]

Issues

1 potential issue found:

• The new public page, nav entry, and two cross-links document content.managed, an internal-stage, default-off feature, under the name "Content management". Public readers can't enable it, and the repo only documents shipped public behavior.
  _{Found by Indent Review Agent}

↑ Select any checkbox above to have Indent auto-fix the issue

CI Checks

All required CI checks passed on 400b4a2.

Review agents

Select any unchecked box below to run or rerun that agent.

Found issues (1)

• Indent Review Agent · Content checks out against the parser, but it publicly documents an internal-only feature.

Full results

Indent Review Agent

• Summary: Content checks out against the parser, but it publicly documents an internal-only feature.
• Last ran on commit: 400b4a23
• Latest result

  {
    "summary": "Content checks out against the parser, but it publicly documents an internal-only feature.",
    "findings": [
      {
        "fix": "Hold the page and the two cross-links until `content.managed` is public, or move this content to the handbook at /features/content, where the feature registry says its docs belong. If it does ship publicly now, use the real feature name (\"Managed content\") and say how a team gets it enabled.",
        "line": 6,
        "path": "content/(dynamic)/content-sync.mdx",
        "issue": "The page opens with \"When Content management is enabled for your team\" and puts the page in the public Dynamic nav, with cross-links from wordpress.mdx and zero-runtime.mdx. The header is only processed for teams with the `content.managed` feature, which the monorepo registry (packages/common/src/contracts/feature-lifecycle.ts) defines as name \"Managed content\", stage \"internal\", defaultEnabled false, enabledForA8c false, and docs channel \"handbook\" (slug /features/content). The control plane gates content releases on `evaluateFeature(\"content.managed\")` (apps/control-plane/src/versions/lifecycle.ts). So public readers get a nav entry and two inline links to a feature they can't turn on, and the page calls it \"Content management\", a name no UI or setting uses. AGENTS.md says this repo documents only \"shipped, publicly verifiable behavior\". I checked the field table, the 2,000/200-byte limits, the status enum, the dateGmt Z/fractional-seconds rules, the future-needs-dateGmt rule, the no-extra-keys rule, the new-document title fallback, and the editor write-back key reordering against the TS and PHP parsers. They all match, so the content is accurate. The problem is that it's published publicly.",
        "title": "Public page documents an internal-only, default-off feature under a name that doesn't exist",
        "severity": "bug"
      }
    ]
  }

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

• Configuration used: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: d9017bd7-9125-4775-9d7a-70a2c8bc8d71

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.}

[indent]

🟡 Bug · Public page documents an internal-only, default-off feature under a name that doesn't exist

The header is only processed for teams with the content.managed feature. The monorepo feature registry (packages/common/src/contracts/feature-lifecycle.ts) lists it as "Managed content", stage internal, default off, with its docs channel set to the handbook (/features/content). The control plane gates content releases on evaluateFeature("content.managed").

Public readers get a nav entry and two inline links to a feature they can't enable, and the page calls it "Content management", a name no UI or setting uses. This repo documents only shipped, publicly verifiable behavior (AGENTS.md).

Hold the page and cross-links until the feature is public, or move the content to the handbook. If it ships now, use the name "Managed content" and say how a team gets it enabled.

_{Found by Indent Review Agent}

[indent]

Confirmed against the feature registry. Closed this public-docs PR and moved the guide to the private handbook in https://github.com/spacefast/contextslop/pull/6, with the content.managed enablement prerequisite. Handbook typecheck, 53 tests, and build pass.

View session