catalogue: batch mysql 9.7.1 + didit 1.0.0 + orthogonal 0.1.1 + smol tombstone (supersedes #356–#359)

[Alexgodoroja]

Why one PR

All four open catalogue PRs modify the same two files — catalogue/catalogue.json and the single-line detached signature catalogue/catalogue.json.sig. Merging any one makes the other three genuinely conflict on the signature line, and the branch-protection setting dismiss_stale_reviews_on_push then wipes their approvals on the required rebase. Result: N merges = N re-reviews.

This PR combines all four so the shared catalogue is regenerated and signed once, reviewed once. It supersedes and closes:

PR	Change	Source of truth here
#359	add io.pilot.mysql 9.7.1	entry + apps/io.pilot.mysql/metadata.json taken verbatim from the PR branch
#358	add io.pilot.didit 1.0.0	entry + apps/io.pilot.didit/metadata.json verbatim
#356	update io.pilot.orthogonal → 0.1.1	entry + apps/io.pilot.orthogonal/metadata.json verbatim
#357	io.pilot.smolmachines → io.pilot.smol tombstone + pilotctl redirect	catalogue tombstone entry, deleted metadata, README.md, cmd/pilotctl/* (incl. appstore_rename_test.go) verbatim

Verification

• catalogue.json regenerated by taking each app entry verbatim from its reviewed branch; diff vs main touches only io.pilot.mysql, io.pilot.didit, io.pilot.orthogonal, io.pilot.smolmachines (+ updated_at). Every other entry is byte-identical.
• Re-signed once with the release catalogue key; derived pubkey matches the embedded catalogtrust.publicKeyB64 and .sig verifies against the exact committed bytes.
• All three metadata_sha256 pins verified against the committed metadata.json bytes.
• go build ./cmd/... passes; #357 rename/tombstone tests pass.

🤖 Generated with Claude Code