[Z-Tons]

What changed

• add one tracker-local, free-form planning note per ticket with workspace-state migration to schema v3
• edit and clear notes only from the shared Ticket Inspector, including read-only repositories
• show note bodies on Frontier, Current Plan, and Waves cards without card-level editing controls
• show compact note indicators in dependency, critical-path, ticket-table, history, and integrity views
• enforce trimming, sanitization, and a 2,000-character limit
• include the approved critical-path summary containment UI fix
• add design/implementation documentation plus unit and Playwright coverage

Why

Users need a generic place to record execution guidance such as which tickets should run at a particular effort level, while still being able to spot annotated tickets throughout the planner.

Impact

Notes remain local to the tracker workspace and do not modify repository tickets, ranking, dependencies, search, or exports.

Validation

• npm test — 95 passed
• npm run build — passed
• npm run test:e2e — 4 passed
• Biome check on all changed code/test files — passed
• Repository-wide npm run lint still reports pre-existing CRLF formatting diagnostics in untouched files