chore: move wiki links to meta/astryx
Update release cadence to weekdays
Release Process: schedule Monday and Thursday releases
Blog rubric: keep criteria canonical
Blog rubric: score human impact and visual evidence
Release process: declare, merge back, then plan next
Release Process: self-grade patch editorial text
Release Process: require explicit minor sign-off
Release Process: shipped package docs need a changeset; name the shared coverage check
docs: preserve post-cut manifest fields in release sync
docs: allow release cuts from checked main ancestors
Require green main before release cuts
Clarify release attempt identity
Clarify process-based release activation
Clarify scheduled release execution mechanics
Clarify release activation and editorial gates
Clarify one-branch release lifecycle
Document fail-closed release branch lifecycle
Document fixed release branches
Document experimental API patch releases
release: extend fallback window to 5 PM
docs: require blog posts for minor releases
docs: limit minor releases to weekly cadence
docs: make public release policy authoritative
Home: reorganize into six sections with progressive disclosure Home listed 40 links across 7 sections while leaving 19 pages unlinked, so it was neither short nor complete. The hub pages that carry each cluster already exist (Component Lifecycle, Vibe Tests, Night Watch Overview, Research Archive); Home now points at them instead of duplicating their contents. - Home: 15 top-level links in Start here / Architecture / Building a component / Quality / Operations / Also. Nothing removed from the wiki — every demoted page is one click deeper behind a hub that lists it. - Add _Sidebar.md so the same navigation renders on every page. - Re-home the four pages Home was the only link to: Blog Review Rubric and Testing Example Apps from Contributing, Hardening Audit Guide from Component Lifecycle. Zero orphans after the change. - Fix the Contributing with AI Assistants link in Release Process, broken by a line wrap inside the [[...]].
Release Process: the release gate is Step 0, and a broken gate blocks the cut
Release Process: codemods are for published packages; lab breaks freely
Correct the build pipeline description: Babel and tsc, ESM-only output core/lab/charts/richtext build with Babel plus tsc, not tsup; core is type: module so there is no CJS bundle or .mjs/.d.mts pair. @astryxdesign/build ships StyleX Babel/PostCSS/Vite plugins, not a tsup config.
Release-Process: codemods stage in transforms/next/ (auto-promoted at version time)
Release protocol: bump the minor for breaking changes while 0.x Match the release tooling change (facebook/astryx#4264): a [breaking] changeset now bumps the minor (0.x.y -> 0.(x+1).0, the breaking tier under caret ranges) and everything else bumps the patch. Update the 0.x semver rule, the changeset bump table, the [breaking] example, and the Distribution versioning section accordingly.