docs: demo modes, staging deploy record, board link; version 0.2.0

[scrimshawlife-ctrl]

Docs and versioning only. No runtime code changes.

What changed

• Version: package.json / package-lock.json 0.1.0 to 0.2.0 for today's demo mode (LOCAL demo: one-command dev:demo, demo seed, /api/v0 smoke, native fixtures #187, demo: easy LOCAL sign-in (demo@example.invalid / 123456) #189) and path-parameter fix (LOCAL demo: one-command dev:demo, demo seed, /api/v0 smoke, native fixtures #187). Implements SUAS-specs 0.6.0 (pin fb27e54). app_version in build-info will read 0.2.0.
• CHANGELOG.md (new): Keep a Changelog style. 0.1.0 is the baseline (e3a9a16, docs: preflight readiness record, SPEC-018 stays blocked #186); 0.2.0 covers LOCAL demo: one-command dev:demo, demo seed, /api/v0 smoke, native fixtures #187, test: staging path-param check for cases/{id}/service-requests #188, demo: easy LOCAL sign-in (demo@example.invalid / 123456) #189.
• RELEASING.md (new): bump, changelog, tag vX.Y.Z on main after an approved merge, GitHub Release.
• .github/workflows/release.yml (new): on a pushed v*.*.* tag, creates the GitHub Release from that version's CHANGELOG section. Builds and deploys nothing. Does not run on PRs or pushes to branches.
• README.md: version and board link in Start here; native demo modes table (Android launchers, iOS Demo and Local schemes); new "Synthetic STAGING deploys" section (manual worker-deploy, staging on 0f7aeae, staging-path-param-check after each deploy).
• AGENTS.md: version, changelog, board pointer; corrected the stale note that LOCAL OTP codes are never retrievable (now dev:demo fixed code and LOCAL-only /api/v0/dev/last-challenge).
• docs/runbooks/cloudflare-workers.md: path-param patch note, deploy record table, post-deploy check, unpinned wrangler follow-up.

Board: https://github.com/users/scrimshawlife-ctrl/projects/6

After Danny approves the merge (do not run before)

cd suas && git checkout main && git pull
# baseline tag on the last commit before 0.2.0 work
git tag -a v0.1.0 e3a9a16 -m "suas v0.1.0 baseline (implements SUAS-specs 0.6.0)"
# 0.2.0 on the merge commit of this PR
git tag -a v0.2.0 <merge-sha> -m "suas v0.2.0 (implements SUAS-specs 0.6.0)"
git push origin v0.1.0 v0.2.0

The release workflow then creates both GitHub Releases from CHANGELOG.md.

Not changed

No deploy, no tag, no settings change. HANDOFF.md untouched. No em dashes in new text.

Merge approval

Danny approved merging this PR on 2026-10-07 at 2:41 PM PT ("Merge suas #190, specs #43, Android #13 and iOS #10, then cut the tags"). Squash-merged after CI was green on the final head.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-07T21:36:28.930785Z	acea4d0	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: acea4d03d1

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Create the baseline release from the current workflow

When the planned v0.1.0 tag is pushed at e3a9a16, this tag-triggered workflow cannot run because GitHub evaluates the workflow from the tagged revision; repository inspection confirms that revision contains neither this workflow nor CHANGELOG.md. Consequently, the promised v0.1.0 GitHub Release will not be created, even though v0.2.0 can be. Create the baseline release manually or provide a workflow_dispatch path on main that accepts an existing tag.

Useful? React with 👍 / 👎.