GitLab

* docs: say plainly how this project is developed

The repo publishes the reasoning behind shipped behaviour and does not publish
plans for unreleased work. That was true but unstated, which reads as opacity
rather than as a boundary; CONTRIBUTING now says which is which, why, and what
contributions are most useful given it.

* dash, type: the unreleased apps say so, in their own READMEs

Source being in the tree is not a product being released, but nothing in either
directory said so — a stranger who built one would reasonably read it as shipped
work that is bad. Each README now states the status, that a local build is
unsigned, and what its shell does about updates: both embed a manifestUrl, so
'cannot update' would have been wrong — nothing is published at those paths yet,
and when one ships, a file built today would offer itself the real release.

dash's registry entry gains the same treatment. It is registered BEFORE it ships
on purpose: release.mjs defaults to --app slides, so listing it claims nothing,
while test-release-apps.mjs proves its manifest URL, changelog shape and unique
ids on every CI run instead of mid-release. That reasoning was the one decision
in apps.mjs carrying no comment.

* docs: working notes moved into subdirectories; references follow

The gitignored working/ notes were reorganised into design/ and launch/, which
left 16 references stale across DECISIONS.md, three app/server READMEs, four
scripts and two source comments. Path-only corrections — no claim changes.

Also ignores .claude/agents and .claude/commands/team, which are local harness
config on this machine. The patterns have no trailing slash on purpose: these
are symlinks, and a trailing slash only matches real directories.