docs: switch author attribution from "Stephen Waits" to SWaits

Per maintainer's preference, the project's outward-facing copy now
refers to the author as [SWaits](https://swaits.com/) instead of
his legal name and email address.

Touched in this commit:
- src/00-overview.md (Status and Provenance callout)
- README.md (Provenance section + Author section; the email
  steve@waits.net is dropped — swaits.com is now the canonical
  contact)
- book.toml (authors = ["SWaits"], plain text since TOML)
- versions/v0.1.0/00-overview.md (regenerated via
  `just cut-version v0.1.0` after src/ was updated)

Git author identity on commit metadata is a separate, git/jj-config
concern and is intentionally not touched.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

README.md

@@ -20,10 +20,10 @@ endorsed by, or maintained by the upstream MeshCore project. Read this section
 before relying on the spec for anything load-bearing.
 
 - **Authorship.** The spec, the corpus, and the tooling were written by Claude
-  (Anthropic, primarily Opus 4.x) under the direction of Stephen Waits.
-  Substantive edits — additions, clarifications, audit passes — are produced
-  through model-driven analysis of the official MeshCore source and reviewed
-  before commit.
+  (Anthropic, primarily Opus 4.x) under the direction of
+  [SWaits](https://swaits.com/). Substantive edits — additions, clarifications,
+  audit passes — are produced through model-driven analysis of the official
+  MeshCore source and reviewed before commit.
 - **Source of truth.** The official MeshCore firmware at
   [meshcore-dev/MeshCore](https://github.com/meshcore-dev/MeshCore) is the
   **golden source of truth** for all protocol behavior. Whenever this spec and
@@ -108,4 +108,4 @@ which together are the authoritative reference this spec derives from.
 
 ## Author
 
-Stephen Waits <steve@waits.net>
+[SWaits](https://swaits.com/)

book.toml

@@ -1,6 +1,6 @@
 [book]
 title = "MeshCore Protocol Specification"
-authors = ["Stephen Waits"]
+authors = ["SWaits"]
 description = "An independent, AI-authored specification and conformance test corpus for the MeshCore mesh networking protocol. The official MeshCore C++ firmware is the source of truth; this spec is downstream."
 language = "en"
 src = "src"

src/00-overview.md

@@ -14,10 +14,10 @@
 > load-bearing.
 
 This document was primarily written by an AI (Claude, by Anthropic — mostly
-the Opus 4.x family) under the direction of Stephen Waits, with human
-proofreading and editing on top. Substantive edits — additions, audit passes,
-errata fixes — are produced through model-driven analysis of the upstream
-MeshCore C++ source and reviewed before commit.
+the Opus 4.x family) under the direction of [SWaits](https://swaits.com/),
+with human proofreading and editing on top. Substantive edits — additions,
+audit passes, errata fixes — are produced through model-driven analysis of
+the upstream MeshCore C++ source and reviewed before commit.
 
 The **upstream MeshCore C++ firmware is the source of truth** for all
 protocol behavior. This spec is downstream and derivative. Whenever the spec

versions/v0.1.0/00-overview.md

@@ -14,10 +14,10 @@
 > load-bearing.
 
 This document was primarily written by an AI (Claude, by Anthropic — mostly
-the Opus 4.x family) under the direction of Stephen Waits, with human
-proofreading and editing on top. Substantive edits — additions, audit passes,
-errata fixes — are produced through model-driven analysis of the upstream
-MeshCore C++ source and reviewed before commit.
+the Opus 4.x family) under the direction of [SWaits](https://swaits.com/),
+with human proofreading and editing on top. Substantive edits — additions,
+audit passes, errata fixes — are produced through model-driven analysis of
+the upstream MeshCore C++ source and reviewed before commit.
 
 The **upstream MeshCore C++ firmware is the source of truth** for all
 protocol behavior. This spec is downstream and derivative. Whenever the spec