Docs: add AAM-aligned monotonic capability roadmap

[dinpd]

Summary

• add a prominent, qualified reference to Cloudflare's Agent Access Model (AAM)
• keep P4 provider trust active and insert P5 monotonic task capability state and protected-result release
• define the held-result, monotonic transition, stale-work fencing, acknowledgement, evidence, and reconciliation/exfiltration demo gates
• move framework distribution to P6 and downstream attribution to P7
• link the open engineering program Program: monotonic task capability state and protected-result release #78 and work packages Define the task execution graph and monotonic capability-state contract #79–Implement durable capability transitions and stale-work fencing in the hosted runtime #83
• add regression tests for the AAM boundary language, roadmap ordering, task links, and local documentation links

Closes #77.

The implementation program remains open in #78. This PR does not claim that AgentPass implements the complete AAM architecture and does not implement runtime capability transitions.

Acceptance evidence

• README contains the AAM link near the top-level product explanation.
• README and roadmap distinguish AgentPass's action-control/evidence role from external identity and network enforcement.
• Roadmap ordering is P4 provider trust → P5 monotonic task capability state → P6 distribution → P7 attribution.
• P5 documents hold/classify/transition/fence/acknowledge/release behavior and the runnable reconciliation/exfiltration completion gate.
• Engineering issues Program: monotonic task capability state and protected-result release #78–Implement durable capability transitions and stale-work fencing in the hosted runtime #83 exist with observable acceptance criteria and security considerations.
• Issue Add downstream agent attribution and provenance labels #75's roadmap placement was updated from P6 to P7.

Validation

• pytest -q tests/test_positioning_docs.py — 7 passed
• pytest -q — 111 passed
• npm test in sdk/typescript — 10 passed
• npm run build in sdk/typescript — passed
• python scripts/check_manifests.py ... — passed for the customer-support, delegation, and provider MCP examples
• git diff --check — passed

Security and review

• No runtime authorization, credential, network, schema, or deployment behavior changes.
• Diff reviewed for overclaiming AAM coverage and explicitly preserves identity/network integration boundaries.
• Diff-level scan found no credential, token, password, or private-key material.
• gitleaks was not available locally; manual diff and pattern scanning were used.
• Protected-result requirements prohibit protected payloads in portable evidence, logs, receipts, and telemetry.