Specify canonical item references and legacy-number migration #79

Work

Inventory task/memory numbering, typed URLs, MCP inputs/outputs, stored Markdown references, batch imports and non-project scopes. Specify a shared public item registry and a stable-ID qualified reference format. Bare #N means the current project only.

Migration decision

Prefer preserving existing task numbers and assign conflicting memories fresh numbers above the current maximum, subject to a complete collision report. Maintain legacy typed memory routes/identifiers without reinterpreting them as new canonical numbers; use a distinct canonical route/contract version where necessary. Historical untyped references remain ambiguous and must be flagged, never guessed.

Acceptance

• Worked examples for task #1 plus memory #1, renamed projects, private/non-project items and archived records.
• Explicit old-to-new mapping, rollback approach and API compatibility window.
• Decision documented before allocator/migration implementation.

Dependencies

First child of #73; planning output required for subsequent children.