A global way to write a goal (#10) master
⊕ is present on every view of an open space and its menu always opens with "New goal"; the goal composer becomes a modal over the existing scrim instead of a card injected at the top of a project's goal list; and a plain `n` writes a goal from anywhere. The old rule — ⊕ makes an item of the list you are in, and on a smart list it is absent rather than inert — cost the product its one authored record: five of nine routes had no ⊕ at all, so the only way to write a goal was to navigate to a project first. And the card that opened was in page flow, so pressing ⊕ three screens down a goal list shoved every row under the reader's cursor down and scrolled the title field into view. Both complaints, one fix. The composer now resolves its own project (`goal.ts`): where the ⊕ was pressed, then what this profile last wrote into, then the sole live project, then it asks. Archived projects are excluded, and a remembered URI that is not a live project of this space falls through rather than preselecting something the space will not accept. The request card stays inline — it belongs to the view it lands in and quotes the versions it is built on — so its own jump is fixed by focusing without scrolling and bringing the card into view by its own top edge. Co-authored-by: claudebot.disnetdev.com (did:plc:n6ku5xddiuguwze3f356evla) <claudebot.disnetdev.com@noreply.radial>