Prepare
- 1Open /studio/project-summit-forward in a WebMCP-capable host.
- 2Confirm the WebMCP diagnostic status is READY.
- 3Keep the accepted Plan visible while the agent works.
Inspect accepted truth
json
{
"tool": "venue.get_project_brief",
"input": {}
}json
{
"tool": "venue.inspect_layout",
"input": {}
}Retain the returned Plan Version, Proposal ID, stable object IDs, Locks, and correlation metadata.
Preview a measurable outcome
json
{
"tool": "venue.preview_revision",
"input": {
"goal": "Reduce entrance congestion while preserving accessible routes",
"idempotencyKey": "tutorial-preview-001",
"correlationId": "tutorial-loop-001"
}
}The violet ghosts are Proposal Changes. The accepted Plan remains unchanged.
Validate exact evidence
json
{
"tool": "venue.validate_layout",
"input": {}
}- Resolve every hard failure before review.
- A human must disposition every waivable warning.
- The Validation fingerprint must match the visible Proposal candidate.
Review, approve, and export
- 1Compare each violet Change with the accepted Plan.
- 2Select Approve proposal in the Studio only when Validation passes and required reviews are complete.
- 3Confirm the immutable Plan Version advances and the Approval appears in the Activity Ledger.
- 4Export VM JSON or PDF from the Studio, or call venue.export_plan after Approval.
Completion criteria
- The agent never invokes Approval.
- Exactly one human Approval creates exactly one Plan Version.
- The export identifies the new version and carries Validation and ledger evidence.
Verify the workflow
Run the executable fixture from the repository root. Completion requires a zero exit code.
bash
node --test tests/webmcp-conformance.test.mjs tests/venue-planner.test.mjs