chore: publish only user-facing documentation on GitHub

Keep maintainer, agent, OpenSpec, and release-engineering docs local-only.
Public tree retains README, community/safety docs, user guides, and examples.
Slim CONTRIBUTING to community rules; drop release/dev sections from README.

Author: bx33661

.gitignore

@@ -12,12 +12,15 @@
 oh-my-codex/
 oh-my-claudecode/
 
-# OpenSpec: publish accepted specs; keep in-progress change drafts local
-openspec/changes/
-# Root historical vision draft only (do not match openspec/**/spec.md on case-insensitive FS)
+# Maintainer / agent / release engineering docs (local only — not for GitHub)
+openspec/
 /SPEC.md
-
-# Agent implementation plans / superseded design drafts (not public product docs)
+/AGENTS.md
+/CLAUDE.md
+/DEVELOPMENT.md
+/RELEASE.md
+docs/architecture/
+docs/roadmap-0.8.md
 docs/superpowers/
 
 # TypeScript build output

.npmignore

@@ -4,5 +4,13 @@
 **/*.pyo
 **/test_*.py
 
-# Keep npm package free of internal agent planning drafts
+# Maintainer-only docs (must not ship in npm)
+docs/architecture/
+docs/roadmap-0.8.md
 docs/superpowers/
+AGENTS.md
+CLAUDE.md
+DEVELOPMENT.md
+RELEASE.md
+SPEC.md
+openspec/

AGENTS.md

@@ -10,7 +10,8 @@ Ship when release notes and `registry.yaml` / `package.json` versions are bumped
 - **SourceRef.v1 + report provenance** — `omv sources init|show|validate` and `omv report provenance` manifests that hash Evidence, reports, and available local dependencies. Missing manifests warn; stale confirmed manifests fail artifact checks.
 - **PatternPack.v1 + unified evals** — 14 JSON pattern-pack manifests (including R/Lua), manifest-driven find/audit asset sync, and `omv eval` with human/JSON/JUnit output.
 - **ThreatMap rich render** — `omv findings show` prints full `source → transforms → sink` paths with confidence, bypassable guards, and summary (no longer collapses to a single source→sink line).
-- **Readiness policy helpers** — `isReportReady` / `isSubmissionScoreReady` / `resolveDoctorNextAction` in `workflow.ts` as the shared report-readiness gate used by doctor and review; maintainer docs (`AGENTS.md`, `CLAUDE.md`, `SPEC.md` banner) aligned with the current tree.
+- **Readiness policy helpers** — `isReportReady` / `isSubmissionScoreReady` / `resolveDoctorNextAction` in `workflow.ts` as the shared report-readiness gate used by doctor and review.
+- **Public docs policy** — GitHub publishes user-facing guides only; maintainer/agent/release docs stay local.
 
 ## v0.9.0 - CLI command split and local findings dedup