task-context: links live in a human-readable "## Related" deep-link section

[renezander030]

What

Typed cross-task links previously lived inside the ats:context JSON block as opaque {type, projectId, taskId} entries — a wall of IDs that means nothing to a human reading the task in TickTick/Obsidian. This moves them to a human-readable ## Related section near the bottom of the task body:

## Related
- depends-on: [Auth spec](https://ticktick.com/webapp/#p/demo/tasks/auth-spec)
- supports: [Q3 launch plan](https://ticktick.com/webapp/#p/demo/tasks/q3-plan)

One line serves both audiences: a human clicks the deep link (Obsidian-style backlink navigation), the agent parses type: [title](url).

How

• Serialization-only change in packages/core/task-context.js (parseTaskMetadata / writeTaskMetadata + helpers). The in-memory link model is unchanged, so ats link, ats graph, ats context, hierarchy, and the event stream all keep working untouched.
• projectId/taskId are recovered from the link URL — the TickTick native deep link (…/#p/<proj>/tasks/<task>), or a generic …/<projectId>/<taskId> form for other adapters' urlFor(). A link written without a url falls back to a parseable ats://task/<proj>/<task> ref so it still round-trips.
• The machine block now holds only intent / lifecycle / security / hierarchy.

Back-compat

Links still inside a legacy JSON block are read (no data loss) and migrate to the ## Related section on the next write.

Tests

• Full suite 180/180 pass, lint clean.
• New: links render as a Related deep-link section (not JSON); machine block carries no link IDs; round-trips into the in-memory model.
• New: legacy JSON-block links are read and migrate to Related on write.
• Existing graph/context/hierarchy/MCP/event tests pass unchanged.

Docs updated in docs/agent-layer.md.

🤖 Generated with Claude Code