docs: unwrap the changelog for release-note rendering

Author: cablehead

changes/v0.5.0.md

@@ -1,36 +1,18 @@
 # v0.5.0
 
-Breaking. The CLI is overhauled: six commands are replaced, and `expose` now
-requires a grantee.
+Breaking. The CLI is overhauled: six commands are replaced, and `expose` now requires a grantee.
 
 ## Where this came from
 
-The CLI had grown a command at a time, as features landed. By 0.4, five of them
-covered one job: getting two machines to talk to each other. `ticket`,
-`grant-token`, `add-peer`, `pin`, `remove-peer`.
-
-So we stopped adding to it. We wrote down what you actually type, on both
-machines, to get a link up. That became `docs/scenarios.md`.
-
-The first flow did not work. Reaching a shared build box from a laptop already
-running a daemon meant sending two values out of band, a key and a token. Neither
-was ever used without the other. `add-peer` could not present a token. `--enroll`
-existed only on `pai-sho daemon`, so a laptop already serving other peers had to
-restart to admit one more. None of it was hidden in the code. It just never came
-up until the whole flow was on one page.
-
-The names took several rounds. `pin` was tried and dropped, along with
-`grant-key` and `allow`/`connect`. Each described a mechanism rather than the
-thing happening, which is closer to: hi, be friends. And: yeah, be friends. That
-is `invite` and `accept`, and the rest followed from the pair. An invitation
-collapsed into one value instead of two, since both halves always travelled
-together anyway. The grant moved onto the invitation: both steps happen
-on the same machine and express one intention. And naming went local. A name is
-what you type into a URL, so it belongs to whoever is typing.
-
-The same exercise turned up the `expose` default-allow. Writing "and then nothing
-is reachable until you grant it" one paragraph away from a command that granted
-to every peer you knew is hard to miss once both are on the page.
+The CLI had grown a command at a time, as features landed. By 0.4, five of them covered one job: getting two machines to talk to each other. `ticket`, `grant-token`, `add-peer`, `pin`, `remove-peer`.
+
+So we stopped adding to it. We wrote down what you actually type, on both machines, to get a link up. That became `docs/scenarios.md`.
+
+The first flow did not work. Reaching a shared build box from a laptop already running a daemon meant sending two values out of band, a key and a token. Neither was ever used without the other. `add-peer` could not present a token. `--enroll` existed only on `pai-sho daemon`, so a laptop already serving other peers had to restart to admit one more. None of it was hidden in the code. It just never came up until the whole flow was on one page.
+
+The names took several rounds. `pin` was tried and dropped, along with `grant-key` and `allow`/`connect`. Each described a mechanism rather than the thing happening, which is closer to: hi, be friends. And: yeah, be friends. That is `invite` and `accept`, and the rest followed from the pair. An invitation collapsed into one value instead of two, since both halves always travelled together anyway. The grant moved onto the invitation: both steps happen on the same machine and express one intention. And naming went local. A name is what you type into a URL, so it belongs to whoever is typing.
+
+The same exercise turned up the `expose` default-allow. Writing "and then nothing is reachable until you grant it" one paragraph away from a command that granted to every peer you knew is hard to miss once both are on the page.
 
 We think this is much nicer to use, and hope you do too.
 
@@ -49,50 +31,27 @@ We think this is much nicer to use, and hope you do too.
 
 ## Highlights
 
-- **`invite` and `accept`.** One side extends an invitation and the other takes
-  it up. Neither works alone. An invitation is one value, `<key>.<code>`: who to
-  dial, and the proof you may. `accept` also takes a bare key. That is the
-  host-attested path from ADR 0003, where no secret travels into the guest. A
-  running daemon can admit a peer without restarting
-  ([ADR 0006](https://github.com/cablehead/pai-sho/blob/v0.5.0/docs/adr/0006-invitations.md)).
+- **`invite` and `accept`.** One side extends an invitation and the other takes it up. Neither works alone. An invitation is one value, `<key>.<code>`: who to dial, and the proof you may. `accept` also takes a bare key. That is the host-attested path from ADR 0003, where no secret travels into the guest. A running daemon can admit a peer without restarting ([ADR 0006](https://github.com/cablehead/pai-sho/blob/v0.5.0/docs/adr/0006-invitations.md)).
 
-- **`expose` requires `--to <key>` or `--all`.** Bare `expose <port>` used to
-  grant to every peer the daemon knew, a default-allow inside a system whose
-  first ADR opens with default deny. `--all` is explicit now, and it means every
-  peer known at that moment, never a standing rule for peers admitted later.
+- **`expose` requires `--to <key>` or `--all`.** Bare `expose <port>` used to grant to every peer the daemon knew, a default-allow inside a system whose first ADR opens with default deny. `--all` is explicit now, and it means every peer known at that moment, never a standing rule for peers admitted later.
 
-- **A pure core.** Admission and authorization moved to `src/core/session.rs`, a
-  state machine with no IO that returns actions for the shell to carry out. The
-  decisions are now reachable from unit tests that run in microseconds, where
-  before they needed two live endpoints and a real listener
-  ([ADR 0007](https://github.com/cablehead/pai-sho/blob/v0.5.0/docs/adr/0007-pure-core.md)).
+- **A pure core.** Admission and authorization moved to `src/core/session.rs`, a state machine with no IO that returns actions for the shell to carry out. The decisions are now reachable from unit tests that run in microseconds, where before they needed two live endpoints and a real listener ([ADR 0007](https://github.com/cablehead/pai-sho/blob/v0.5.0/docs/adr/0007-pure-core.md)).
 
-- **`list` says how each peer arrived**, by code or by key, since the two carry
-  different weight when auditing who is on your network.
+- **`list` says how each peer arrived**, by code or by key, since the two carry different weight when auditing who is on your network.
 
 ## Fixes
 
-- `add_peer` dialed before recording the peer. A failed dial left nothing behind,
-  so there was no peer and nothing to retry, and a flow `docs/scenarios.md` said
-  should work silently didn't. It records first now.
-- A failed port bind was logged and dropped, on the theory that the next announce
-  would retry it. A peer with a stable port set never re-announces, so the port
-  stayed dark until something else changed. Binds now retry.
+- `add_peer` dialed before recording the peer. A failed dial left nothing behind, so there was no peer and nothing to retry, and a flow `docs/scenarios.md` said should work silently didn't. It records first now.
+- A failed port bind was logged and dropped, on the theory that the next announce would retry it. A peer with a stable port set never re-announces, so the port stayed dark until something else changed. Binds now retry.
 
 ## Tests
 
-72 tests, from a suite that could not reach the security decisions at all. Unit
-tests in `core` cover admission, grants, and tunnel authorization; `live_tests.rs`
-runs two real daemons over loopback with relays disabled for dialing,
-reconnection, binding, and eviction. Mutation testing confirms they bite:
-replacing the grant check with `if true` fails five tests.
+72 tests, from a suite that could not reach the security decisions at all. Unit tests in `core` cover admission, grants, and tunnel authorization; `live_tests.rs` runs two real daemons over loopback with relays disabled for dialing, reconnection, binding, and eviction. Mutation testing confirms they bite: replacing the grant check with `if true` fails five tests.
 
 ## Docs
 
-- `docs/scenarios.md` works two flows end to end, a shared build box reached from
-  a laptop and a laptop booting a vibenv, with the invariants each depends on.
-- New ADRs 0006 (invitations) and 0007 (pure core). 0002 and 0004 carry notes
-  where their vocabulary no longer matches what shipped.
+- `docs/scenarios.md` works two flows end to end, a shared build box reached from a laptop and a laptop booting a vibenv, with the invariants each depends on.
+- New ADRs 0006 (invitations) and 0007 (pure core). 0002 and 0004 carry notes where their vocabulary no longer matches what shipped.
 - README, `--help`, and the crate description rewritten.
 
 ## Raw commits