Release v1.11.0 with a living outcome-led roadmap

[sergeliatko]

Summary

Replace the completed seven-phase roadmap as current direction with a living outcome-led roadmap that ranks current product outcomes, defines how evidence becomes work, and keeps exact delivery state in GitHub.

Preserve issue #6, phase issues #7 through #13, and the founding delivery record as history. Add Program Decision 0006, update the related architecture, governance, maintenance, evidence, provenance, contribution, testing, navigation, and version surfaces, and validate the new roadmap boundary.

This closes #46.

Contract Impact

• Activation or non-activation boundary
• Runtime workflow or output
• Safety, privacy, or permissions
• Host capability or installation guidance
• Reference knowledge or fixtures
• Validation, packaging, CI, or release
• Documentation or community files only

Validation

• Ran npm run validate
• Ran npm run package -- v1.11.0
• Ran npm run release:verify-assets -- v1.11.0
• Ran npm run release:preflight -- v1.11.0 on the final uncommitted tree
• Inspected standalone, Codex, and Claude ZIP contents
• Confirmed the installed runtime tree is unchanged from v1.10.0
• Reviewed affected activation, behavior, and adversarial fixtures and confirmed that no runtime invariant changed
• Checked for secrets, private repository data, local paths, and placeholders

Quality Review

• Architecture and maintainability remain healthy
• Security and privacy remain healthy
• Agent behavior and evaluation remain healthy
• Teaching and user learning remain healthy
• Governance and sustainability remain healthy

Traceability

• Issue: Replace the completed phase roadmap with a living maintenance roadmap for v1.11.0 #46
• Program decision: 0006
• Current roadmap: docs/ROADMAP.md
• Historical delivery: docs/ROADMAP-DELIVERY.md
• Release notes: v1.11.0

Decisions and Follow-Up

GitHub issues and pull requests remain the canonical delivery state; the roadmap contains durable outcomes, selection rules, evidence boundaries, review ownership, and recovery. Feedback and outcome evidence remain candidate inputs rather than accepted tasks.

The final preflight passed with release-tree SHA-256 e65fc8be69181669072f231cfa9d7a67774b62493936abf297e0772bf74ad9c4 and checksum-manifest SHA-256 41d63a941bc8731360529a22e40e6de61b992f247d5321b44115fb2d682ce001.

No release tag or public release has been created. After review and squash merge, the release owner must authorize the annotated v1.11.0 tag and later publication of the generated draft separately.