Ack: block-roadmap.md integration contract (bridges, IRIs, fixtures)

[aharlap]

Acknowledging the Proof-side obligations from the workspace's docs/block-roadmap.md (v0.1, July 2026) — the blocks↔Proof integration contract:

Accepted and acting now (Milestone 3):

• Align question sub-activity IRIs to the contract: p.js emits {activityIri}/q/{questionId} (was /questions/; zero external embedders, so this is the last free rename). Steps stay {activityIri}/steps/{id}; the dashboard also honors step labels carried in progressed extensions per §2.4.
• Dashboard verb semantics per §2.4: passed/failed treated as success signal alongside completed/scored; registration groups attempts.
• Bridge-session statement fixtures per §2.4 land in prax-proof's test suite now; they are the seed for the canonical prax/examples/ fixtures (§2.8), which don't exist yet.

Accepted, scheduled later:

• Bridge B ownership acked (§2.2, open question 4): the data-prax auto-binding mode of p.js is a Proof deliverable. Blocked on the event-vocabulary extensions (prax:answer, progress.step, score.success) landing in the prax spec (~Sep 2026 per roadmap §8).
• Answer encoding alignment (open question 7): when Bridge A exists, proof.answer() and the xAPI facade serialize result.response identically (xAPI interaction encodings). Until then the dashboard renders responses as opaque strings.
• sendBeacon/keepalive for end-of-session statements (§2.6): p.js already uses keepalive fetch; revisit for the data-prax adapter.

🤖 Generated with Claude Code