Update README.md

[bryanfawcett]

Summary

Linked issue(s)

Closes #

Type of change

• feat — user-visible new feature
• fix — user-visible bug fix
• perf — performance improvement
• refactor — code change, no behaviour change
• docs — documentation only
• test — tests only
• build — build system, packaging, dependencies
• ci — CI configuration
• chore — maintenance
• revert — revert of a prior commit

Breaking change?

• This PR introduces a breaking change.

How has this been tested?

Checklist

Process

• My PR title follows Conventional Commits.
• All of my commits are signed and show "Verified" on GitHub
  (GPG or SSH). See
  CONTRIBUTING.md § Signed commits.
• All of my commits have a DCO sign-off (Signed-off-by: trailer,
  added by git commit -s).
• My branch name follows <type>/<short-kebab-description> (see
  CONTRIBUTING.md § Branch naming).
• I have rebased onto the latest default branch; no merge commits
  from the base branch in this PR.
• I have added or updated tests covering the change (or explained
  below why tests aren't applicable).
• I have updated documentation (README, inline docs, changelog,
  migration notes) where relevant.
• I ran the repo's local checks (lint, typecheck, tests) and they pass.
• Any new runtime dependencies are justified in this PR description
  (name, version, license, why).
• If this is a breaking change, I have marked the box above and
  included a BREAKING CHANGE: footer in at least one commit.

NA-03 merge blockers

• N/A — this change does not touch schema, APIs, dependencies,
  cryptography, data placement, or smart-contract counts.
  (If ticked, skip the remaining boxes in this section.)
• Secret hygiene — I confirmed no API keys, tokens, .env contents,
  private keys, or credentials appear anywhere in the diff.
• Prohibited dependencies — this PR introduces no Flutter,
  Couchbase, or CouchDB-as-datastore dependency, and contains no
  reference to a fixed 10-billion MXT supply cap.
• Schema.org compliance — new database tables, columns, or API fields
  map to Schema.org types, or the PR description justifies any deviation.
• Locked counts respected — no change to the platform's locked counts
  (17 mini-apps · 7 data layers · 7 covenants · 40 interest categories ·
  12 manifesto sections · 3 sources of truth) without Founder approval
  documented in the PR description. Nyuchi Enterprise products are
  not a locked count (NA-03 §3.3) — do not re-add a count for them.
• Frontier defaults — for user-facing or infrastructure work:
  offline / local-first behaviour has been considered; any new
  cryptographic primitive has a documented post-quantum migration path;
  edge-native placement has been addressed.
• New GitHub Actions are pinned to a 40-character commit SHA
  (not a floating tag) per NA-03 §7.1.1.

Screenshots / recordings

Additional notes