chore: evaluate Omnigent project template and installer path

[smota]

Epic: #27

Summary

Evaluate how adopting projects should install Omnigent-aware multi-agent-sdlc setup: this repo, Omnigent templates, or both.

Acceptance criteria

• Architecture note documents ownership options for an Omnigent SDLC project template.
• Proposed install flow includes AGENTS.md, agent-workflow.config.json, docs/templates/hooks/validators, GitHub Actions, and Omnigent policy examples.
• Cross-repo Omnigent work is captured as follow-up issues rather than hidden TODOs.

Test plan

• Run pnpm format:check.
• Review against existing init/sync/doctor behavior.

Workflow classification

• Type: chore / dx / tooling / documentation
• Suggested profile: standard
• Default execution: single-agent

[smota]

Corrected issue labels after provenance review:

• replaced incorrect drafted-by:claude with drafted-by:pi because these issues were created by the current Pi runtime;
• removed over-applied documentation where documentation is a supporting deliverable rather than the primary work;
• left documentation on chore: document Omnigent-powered SDLC scenarios #31 because that child issue is documentation-first.

Follow-up structural fix opened as #34.

[github-actions]

Integrated into development by PR #35: https://github.com/smota/multi-agent-sdlc/pull/35

Merge commit: 2866f00a11e2d38d291c0b440cdd521ec8c78f81
Release/promotion to main is tracked separately.