kwakseongjae Expiry. This gate is a waiting state, not a policy. It lifts when the
catalog adoption path lands — the T2-2 writer gate, tracked in
docs/OMD_PLAN_2026-09-02.md §0 "카탈로그 채택 경로" (today: 없다 — the migrated
bodies sit in docs/design-md-weight/migrated/ and web/references/ is still
legacy). Until a graph-backed Core v2 writer exists and every catalog reader
accepts its package, this skill refuses catalog writes — all of them, with no
one-off exception and no plausible fallback.
omd:migrate — catalog write safety gate
CORE_V2_CATALOG_WRITE_BLOCKED
Do not mutate web/references/<id>/DESIGN.md, its frontmatter, numbered
sections, verification footer, or mirrors. Those files remain readable during
the migration window, but creating more legacy bytes would violate the Core v2
dual-read/single-write contract.
For a provider-free assessment, use the Core migration auditor in check mode.
Do not adopt or overwrite its staged result. A migration candidate keeps the
source DESIGN.md canonical until a graph-backed catalog writer, migrated
consumers, evidence binding, and dropped_segments=0 acceptance ship together.