moving

docs/PM-SYNC-PRE-DAY0-2026-05-05.md

@@ -1,5 +1,11 @@
 # PM Sync — Pre-Day-0 Two-Repo Survey
 
+> [!CAUTION]
+> **ARCHIVED / SUPERSEDED — DO NOT EXECUTE.** This May 2026 snapshot predates
+> the curated-forward-port policy. Raw subtree/export publication recommendations
+> are invalid; current authority is `AGENTS.md` §7.5 and
+> `packages/hive-mind-core/CONTRIBUTING.md`.
+
 **Date:** 2026-05-05
 **Scope:** `D:\Projects\waggle-os` (proprietary monorepo, branch `main`) + `D:\Projects\hive-mind` (Apache 2.0 OSS, branch `master`)
 **Author:** CC inventory pass, no mutations to either repo
@@ -409,6 +415,11 @@ A `feat/sync-to-waggle-os-workflow` branch already exists in hive-mind (origin s
 
 ### §8e — Dangling concerns (not raised by PM Claude)
 
+> **CORRECTION (2026-08-22):** Item 1's raw subtree-push recommendation is
+> invalid and must not be executed. Reconcile the public mirror only through a
+> reviewed maintainer-curated forward-port that excludes private files and
+> interleaved `install_audit` logic.
+
 The following are observations from code-side that PM-Claude wouldn't have visibility into. Each surfaces a real risk that should be tracked.
 
 1. **OSS export sync drift is the #1 launch-comms risk.** Day 0 marketing will likely point at `https://github.com/marolinik/hive-mind` as the canonical OSS repo. That repo's master is **8-11 days behind** what waggle-os has prepared in the 12 oss-export branches (Wave-1 doctor command + Windows Quirks docs + postinstall + mcp-health-check; Apache 2.0 boundary + CONTRIBUTING; OSS subtree split + import sweep + smoke). External eyes landing on hive-mind master will see a less-polished extraction than the one PM-side comms might describe. Recommend: subtree-push the 12 oss-export branches into hive-mind master + bump to v0.2.0 + republish to npm BEFORE Day 0 comms go live.