perf: report a daemon that is not ready yet as starting

[MattDHill]

A daemon ready check that isn't satisfied yet now returns starting instead of loading, in the MySQL sidecar check. The "Initializing fresh schema" state stays loading: it is long-running progress with a message the UI shows for loading and hides for starting.

loading means operational but catching up, and start-sdk's default trigger re-polls it every 30 s. A sidecar that reported loading on an early probe therefore held every daemon requiring it for up to 30 s after it was ready. starting is re-polled every second. The pattern came from the packaging guide's Postgres example, corrected in Start9Labs/start-technologies#4272. Start9Labs/start-technologies#4273 makes the SDK back off loading instead, for packages that don't change.

No version bump: master's 6.71.0:0 isn't on beta yet, so this ships with it. Its release notes gain "Performance improvement", placed before the upstream link.

Per helix-a's review, README's first-run notes now describe MySQL as starting until it accepts queries, and Ghost's schema creation as loading.

Verified: tsc --noEmit, Prettier and make javascript/index.js pass. Not installed on a box.

🤖 Generated with Claude Code

[helix-a]

The readiness change itself looks correct. One documentation correction is needed: README.md's Installation and First-Run Flow still says both startup checks report loading with explanatory messages throughout. MySQL now reports starting; the proposal updates that sentence and preserves Ghost's schema-initialization loading description. instructions.md does not describe these states and needs no change.

Verified: clean merge with origin/master via merge-tree; SDK 3.0.6 matches npm's latest; beta serves 6.70.0:0 and does not yet serve 6.71.0:0, so keeping the version is appropriate. Ran npm install, tsc --noEmit, Prettier on the changed TypeScript files, and git diff --check. Reused successful x86 and arm package-build CI for head 00eb9ab. No runtime testing performed.

Proposed changes: 00eb9ab...proposal/51

Helix-Harness: pi
Helix-Model: openai-codex/gpt-6.1-sol

[helix-a]

The README correction resolves my earlier request: it now distinguishes MySQL's starting state from Ghost's schema-initialization loading state. The updated tree exactly matches the previously verified proposal; no further findings.

Rechecked mergeability with origin/master using merge-tree, git diff --check, SDK 3.0.6 against npm's latest, and that beta still does not serve 6.71.0:0. Both x86 and arm package-build CI jobs passed on the new head 6b6373b. Reused the earlier successful typecheck and changed-TypeScript formatting checks; the only follow-up change is documentation. No runtime testing performed.

Helix-Harness: pi
Helix-Model: openai-codex/gpt-6.1-sol