Docs finalization: full pipeline docs sync - #25
Conversation
…S Build refresh - README/AGENTS: full pipeline phases (4.5/4.6/5), fix broken April links - docs/+mkdocs: pipeline diagram + how-it-works phases 4.6/5 - remove April (never an official release) from world-facing: output/2026-04_april_newsletter.md + release_bundle/2026-04_newsletter_launch/ - May bundle: genericize April links, templated pinned command examples - May newsletter: MS Build guide adds KEY01 opening keynote, swaps BRK241->LIVE158 - security: sanitize 3 local paths in .github research prompt; publisher now scans the hidden .github/ tree (--hidden) that was previously unscanned - publisher: --world-facing flag + public_snapshot_worldfacing_prune.txt
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a8ddd04b8e
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| release_bundle/2026-04_newsletter_launch/ | ||
| output/2026-04_april_newsletter.md |
There was a problem hiding this comment.
Stop allowlisting deleted April artifacts
These April paths are now deleted from the source repo, but they are still present in tools/public_snapshot_allowlist.txt, and the publisher only prunes them when --world-facing is passed. In the default publish path, a target repo that already has the April newsletter or launch bundle will just emit WARN missing path, skipped during sync and keep the stale public copies, so the “April never shipped” cleanup is incomplete unless every caller remembers the new flag. Move these paths to the common prune list or remove them from the default allowlist as part of the deletion.
Useful? React with 👍 / 👎.
NEWSLETTER_SYSTEM_RELEASE_NOTES.md gains a 'Changes Since the February 2026 Release' section so it doubles as a standard release readout of every system + repo change since the Feb 2026 release (system-at-a-glance, March-April, May, June finalization, kb/source intel), cross-linked to the existing cost-optimization subsections. April cycle described as world-facing-excluded but retained in the GitHub-employee snapshot. Bundle README read-path updated.
Sanitize the world-facing repo of phrasing and files that exposed the internal publishing tiers. Remove the publishing runbook and snapshot machinery (publish_public_snapshot.sh, public_snapshot_*.txt, public_repo_guide.md), drop the publish wrapper make target, and reword docs to remove 'customer-safe', 'public catch-up', 'private source repository', and the staging-vs-world-facing snapshot distinction.
Summary
Finalization, sanitization, and documentation-sync pass for the world-facing repo.
Documentation
README.md/AGENTS.md: describe the full pipeline including optional phases 4.5 (polishing + deprecation consolidation), 4.6 (video matching), and 5 (editorial review). Removed broken April-bundle links and genericized April examples.docs/+mkdocs.yml:how-it-works.mdand thearchitecture.mdpipeline diagram now include phases 4.6/5 (MkDocs site is source-owned and propagated;mkdocs build --strictpasses).Sanitization
output/2026-04_april_newsletter.mdandrelease_bundle/2026-04_newsletter_launch/..github/prompts/research_system_report.prompt.md, and extended the publisher's sensitive-pattern scan with--hiddenso the allowlisted-to-public.github/tree is scanned (ripgrep skipped it by default, so the leak was previously undetected).Newsletter content
output/2026-05_may_newsletter.md: added the KEY01 opening keynote (Satya Nadella, Jun 2), swapped the BRK241 session for LIVE158 "New coding models optimized for GitHub Copilot" (Jun 3).Tooling
--world-facingflag +tools/public_snapshot_worldfacing_prune.txtthat strips April for the world-facing repo only.Validation
make test-all: all required suites pass..github/): pass.make validate-newsletter FILE=output/2026-05_may_newsletter.md: PASSED, 0 warnings./Users/local paths remain in tracked content.