refactor(sync): align phase 7 record transport

[h4yfans]

What

Align phase 7 sync transport around record-only manifest, changes, and pull flows; update desktop consumers; and add telemetry and regression coverage for the split record vs CRDT paths.

Why

The projection-pipeline work needs the sync server and desktop client to agree on which payloads belong to record transport versus CRDT transport. This also preserves correct note-link state when the last wiki link is removed from a note.

How

• add record-specific sync API schemas and contract coverage
• restrict sync server manifest, changes, and pull handling to record transport payloads and required clocks
• update desktop sync consumers to use the narrowed record transport responses
• separate telemetry domain type reporting for record vs CRDT paths
• add regression coverage for clearing note links when a note no longer contains wiki links
• update the architecture reset checklist to reflect the new boundary

Type

• feat
• fix
• refactor
• style
• perf
• test
• chore
• docs
• ci

Test plan

• Unit tests added/updated
• Integration tests added/updated
• Manual testing

Commands run:

• pnpm --filter @memry/desktop exec vitest run --config config/vitest.config.ts src/main/vault/note-sync.test.ts
• pnpm --filter @memry/sync-server exec vitest run src/foundation-contracts.test.ts src/routes/sync.test.ts src/services/sync.test.ts src/services/sync-telemetry.test.ts
• pre-push pnpm test hook on git push -u origin memry/align-sync-server-phase-7

Screenshots

N/A

Checklist

• Self-reviewed the diff
• No hardcoded secrets or credentials
• Files stay under ~500 LOC
• Follows immutable data patterns