Decide whether agent-governance files should ship in scaffolded consumer projects #47

Summary

Generated/scaffolded Expo projects receive agent-governance files (AGENTS.md, GOVERNANCE.md, workspace reference systems) as part of the template content. It is unclear whether shipping these into consumer projects is intentional; if so it needs documentation, if not it should be excluded from the published template.

Evidence

• Repository: coderooz/expo-template-coderooz @ 18d0a985 (main).
• Template root contains AGENTS.md, GOVERNANCE.md, .opencode/, .workspace-style reference content (uncommitted changes touch AGENTS.md among 110 entries).
• Analysis: .reports/ecosystem/DUPLICATION_ANALYSIS.md (case 7 � governance files in generated projects), .reports/ecosystem/ARCHITECTURE_REVALIDATION.md �3.

Impact

• Severity: Low�Medium.
• Consumers who scaffold from the template inherit this repo's internal agent-governance conventions, which may be unwanted noise or may conflict with their own tooling. Affects what npx create-expo-app -t effectively ships once publishing resumes.

Root Cause

Template was bootstrapped from the internal development environment, and internal governance files were never classified as "template content" vs "repo-internal".

Proposed Resolution

Decide per file class: (a) template content (ships), (b) repo-internal (excluded via package files/.npmignore), (c) optional sample (documented opt-in). Document the decision in template README.

Acceptance Criteria

• Explicit classification list for governance files (ship/exclude/optional).
• .npmignore/files rules match the classification.
• Published package contents verified (npm pack --dry-run) after reconciliation (depends on EXT#40).

Dependencies

• RELATED: EXT#40 (published template stale), EXT#43 (version inconsistency), EXT#46 (namespace decision � publish must wait).

Risk and Rollback

Classification-only change; reversible before publish.

Execution Evidence

2026-10-12: baseline inspection; governance files present in template root.