Context
Phase 547 / PR #218 added the first internal renderer-neutral whiteboard primitive model skeleton. Phase 548 / PR #220 adds the first internal renderer-neutral renderer adapter and hit-testing skeleton. Phase 549 / PR #222 adds the persistence decision gate that keeps current whiteboard primitives outside the current GraphDocument schema and records a separate annotation surface decision.
The next tracker-backed slice in the React Flow parity roadmap is Phase 550: a whiteboard primitive Cookbook screenshot implementation gate. This must provide visual-proof plumbing for future whiteboard primitive examples without widening runtime drawing/tool activation claims or adding unproven persisted whiteboard state.
Scope
Add a bounded Cookbook/screenshot implementation gate after Phase 549:
- define the minimum Cookbook route and screenshot manifest contract needed to prove future whiteboard primitive visual evidence;
- add focused docs/tests that require Phase 550 tracker IDs and preserve stack ordering behind Phase 549;
- if implementation remains proof-only, use existing fixture/catalog routes and metadata rather than adding runtime drawing state;
- keep route metadata, shell state, before/after evidence expectations, and non-overlap requirements explicit;
- keep any Avalonia pointer coordinator, toolbar activation, eraser behavior, persisted state, public drawing API, and full whiteboard parity claim as separate follow-ups.
Out of scope
No new public drawing API, no pointer coordinator edits, no toolbar/tool activation, no eraser behavior, no persisted whiteboard primitive state, no GraphDocument schema change, no schema version bump, no renderer rewrite, no UI redesign, no retained API removal, and no full React Flow whiteboard parity claim.
No screenshot manifest expansion should be merged unless focused failing tests prove the exact Cookbook/screenshot contract and the PR body calls out route metadata, shell state, and visual-proof boundaries explicitly.
Dependency / stacking
Depends on Phase 549 / PR #222 and therefore on the earlier Phase 537-549 stack. This may be implemented as a stacked branch based on feature/phase-549-whiteboard-persistence-decision, but it must not merge before PR #222 and the earlier stack land.
Context
Phase 547 / PR #218 added the first internal renderer-neutral whiteboard primitive model skeleton. Phase 548 / PR #220 adds the first internal renderer-neutral renderer adapter and hit-testing skeleton. Phase 549 / PR #222 adds the persistence decision gate that keeps current whiteboard primitives outside the current
GraphDocumentschema and records a separate annotation surface decision.The next tracker-backed slice in the React Flow parity roadmap is Phase 550: a whiteboard primitive Cookbook screenshot implementation gate. This must provide visual-proof plumbing for future whiteboard primitive examples without widening runtime drawing/tool activation claims or adding unproven persisted whiteboard state.
Scope
Add a bounded Cookbook/screenshot implementation gate after Phase 549:
Out of scope
No new public drawing API, no pointer coordinator edits, no toolbar/tool activation, no eraser behavior, no persisted whiteboard primitive state, no
GraphDocumentschema change, no schema version bump, no renderer rewrite, no UI redesign, no retained API removal, and no full React Flow whiteboard parity claim.No screenshot manifest expansion should be merged unless focused failing tests prove the exact Cookbook/screenshot contract and the PR body calls out route metadata, shell state, and visual-proof boundaries explicitly.
Dependency / stacking
Depends on Phase 549 / PR #222 and therefore on the earlier Phase 537-549 stack. This may be implemented as a stacked branch based on
feature/phase-549-whiteboard-persistence-decision, but it must not merge before PR #222 and the earlier stack land.