content: promote 12 stable drafts to published#68
Merged
Conversation
Mark 12 content pairs (24 files) as published ahead of the first public promotion: 2 concepts, 6 guides, 1 evangelism piece, and the curated index with its 3 entries. All have EN/ZH parity, no placeholders, and source-traceable external claims. Two guide pairs remain draft — agent-ready-repo and agents-md-as-source-of-truth — because they still contain project-specific references outside callouts and fall under SPEC 006 Phase 2 generalization work that has not landed yet.
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Align the 16 promoted pairs whose lastUpdated still pointed to April with the promotion date. Since lastUpdated feeds JSON-LD dateModified, sitemap lastmod, and RSS pubDate, these pages would otherwise broadcast stale timestamps to subscribers and search engines on first public promotion. The 8 files already dated 2026-05-07 (skills-ecosystem, proactive-agent- review, new-repo-setup, css-variable-consistency) are left untouched.
wilsonwangdev
added a commit
that referenced
this pull request
May 8, 2026
## Summary Closeout for the AEO baseline workstream (#69, #70). Captures the process failure that surfaced mid-session and updates the pre-work checklist to prevent recurrence. ## Why this exists While shipping #69 and #70, both PRs initially carried two orphan commits from a stale local branch whose contents had already squash-merged to `main` as #68. Different SHAs hid the equivalence from `git fetch -p`. The reviewer caught it; both PRs were rebased onto `origin/main` and force-pushed. The journal entry is the third PR-hygiene failure recorded. The pattern across all three: rules exist, but the procedural trigger points where rules must fire are under-specified. ## Changes - `journal/2026-05-08-stale-branch-base-pollution.md` — what happened, root cause, fix, evolution notes (EN+ZH). - `AGENTS.md` Git Workflow — new pre-work step 9: explicitly verify `git branch --show-current` returns `main` right before `git checkout -b`. Squash-merge makes stale-branch detection unreliable via SHA; this is a terminal-state assertion rather than a sequence of actions. - `ROADMAP.md` — check off #67, #69, #70; add "AI visibility / AEO content guide" as the next content item (the planned Layer 1 guide that closes this workstream). ## Manual follow-ups (tracked separately, not in this PR) External submissions that require login and cannot be automated from the repo: - [directory.llmstxt.cloud](https://directory.llmstxt.cloud) / [llmstxt.site](https://llmstxt.site) / [llms-txt-hub](https://github.com/thedaviddias/llms-txt-hub) — submit llms.txt URL - Bing Webmaster Tools — register + submit sitemap (unlocks AI Performance panel with citation counts) - Google Search Console — verify AI Overview citation visibility - [Perplexity Publisher Program](https://pplx.ai/publisher-program) — submit site for source consideration These will be handled out-of-band. The handbook's technical readiness for them shipped in #69 and #70.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Promote 12 content pairs (24 files) from
status: drafttostatus: publishedahead of the handbook's first public promotion.What changes
Each pair has verified EN/ZH parity (matching line counts, no placeholders), source-traceable external claims, and uses the SPEC 006 callout pattern when referencing this project.
What stays draft
Two guide pairs remain draft because they still contain project-specific references outside callouts — unfinished SPEC 006 Phase 2 generalization work:
guides/agent-ready-repo— references.claude/settings.jsondirectly in the universal bodyguides/agents-md-as-source-of-truth— contains first-person project history ("We initially used CLAUDE.md...")These should be generalized in a follow-up PR before promotion.
Verification
npm run build→ 28 pages built, no errorsgrep -r "^status:" content/→ 24 published, 4 draft (expected)Note on visibility
The build system (
build/build.mjs) only filtersstatus === 'hidden', notdraft. These pages were already live on the site; this PR updates the frontmatter to match reality and clears the way for futurestatus:based filtering.