/omd-component-harvest

name: omd-component-harvest
description: "Legacy catalog component writer safety gate. Use when component harvesting is requested, but stop before editing until the Core v2 graph-backed catalog writer and readers are available."

**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:component-harvest — catalog write safety gate

`CORE_V2_CATALOG_WRITE_BLOCKED`

Do not rewrite a reference section, legacy frontmatter token block, mirror, or quality marker. The current public catalog is dual-read source material, while all future writers must be graph-backed Core v2. Reusing the retired section and frontmatter mutation path would create a new legacy authority and can silently lose provenance.

Report that component harvesting is temporarily read-only. Evidence collection may be proposed separately, but no catalog bytes may change until a canonical catalog graph/evidence writer, migrated readers, and a provider-free `dropped_segments=0` migration gate ship together.