work-maplisted

# work-map: the map for multi-session efforts A `session` handoff carries one session's baton. A work map preserves one canonical route per effort: the sufficient parent issue, a declared project document or a link-only fallback. Read the repository's `Repository process` declaration first. If absent, use an existing owner or propose the route in chat; never invent one. Its declared workflow-state owner holds live state; this map never does. In `issue-tracker` mode, if the parent issue has enough destination, route and invariant detail, the parent tracker issue is the work map: link to it and do not create a duplicate file. In `project-docs` mode, use its named map or story home. A link-only file is only an unavailable-tracker or cross-tracker fallback. It links owners and never restates current status, owner, dependencies or user gates. ## Optional link-only map Create a file only for `project-docs` or an unavailable/cross-tracker fallback. A docs fallback may use `docs/efforts/EFFORT-<slug>.md` when authorised. ```markdown # EFFORT: <name> ## Destination What the route is intended to deliver. Link the owning specification. ## Route - [Programme issue](https://example.invalid/issues/1) - [Related delivery](https://example.invalid/pull/2) ## Invariants - [Governing decision](https://example.invalid/decisions/1) ``` ## Rules - **Link, never restate live work state.** Do not add status fields, task checkboxes, completion claims, owner names, dependencies, blockers o