Epic: reposition README and documentation IA as product landing path

[smota]

Release 1 aligned record

Release 1 documentation and public website now position AgentFlow SDLC as a product: core SDLC model, publish-grade npm package, harness ecosystem, and optional first-class Cockpit Goal Command Center.

Current product model

AgentFlow SDLC Release 1 is a GitHub-centered product for reviewable AI-assisted delivery. It includes:

• Canonical SDLC definition, config, paths, gates, and validators.
• Publish-grade npm package and release validation gates.
• Harness-neutral skills plus Claude, AGY, Codex, and Pi adapters.
• Structural settings merge and plugin manifest validation.
• Cockpit as optional first-class Goal Command Center: package/release-gated, runtime opt-in, no unique SDLC state.
• Public multi-page website at C:/Code/movetheneedle/site/agent-sdlc.

Acceptance criteria

• README and public site explain what AgentFlow is within first screen.
• Docs and site separate product landing, conceptual explanation, install/adoption, Cockpit operations, and harness ecosystem.
• Cockpit is presented as optional at runtime but first-class in v1 strategy.
• Release 1 website is multi-page and screenshot-ready.

Evidence

• Website commit 6569e8f in movetheneedle site: multi-page Release 1 product site.
• AgentFlow implementation through 2d41931: Cockpit first-class optional v1 product.
• Council input from Claude + AGY incorporated: close stale doc tickets, keep site thin marketing/IA layer, add Cockpit page and setup path.

Outcome

Completed for Release 1. This issue is closed as part of the current whole-model alignment. Future copy refinements should use new issues, not legacy retrofit compatibility.

[smota]

AgentFlow whole-model alignment

This issue was aligned with the current AgentFlow SDLC product model for screenshot/demo consistency.

• Product area: product:docs, product:harness, product:sdlc-core
• Release assignment: future / release:future
• Workflow state: Backlog/future candidate; not required for v1 release gate.
• Compatibility rule: GitHub/CLI durable workflow remains authoritative; generated harness surfaces stay adapters only.

No implementation change is implied by this metadata-only alignment comment.