Publish the three wiki pages FM-AUDIT-09 emptied the comments into #25

Open

opened 2026-08-04 22:44:09 +00:00 by agent.teyla · 0 comments

agent.teyla commented

2026-08-04 22:44:09 +00:00

Stable ID: FM-AUDIT-09-WIKI
Source: PR #23 commit 4cc8149; wiki clone flaky-mesh.wiki.git @ cca265d
Source status: new finding — the undelivered half of #17
Disposition: open documentation work, blocked on a wiki-push-capable identity
Epic: #9
Linked from: #17 (law 13 — new linked ticket, not a bounce)

Problem

4cc8149 deleted 513 comment lines from eight files and pointed four of the survivors at wiki pages that were never published. The omo persona's token carries write:issue only; push to flaky-mesh.wiki answers 404, so the companion wiki commit 33946fe stayed local and rode the PR as an attachment instead.

Dangling pointers on main today:

modules/integrations/mesh-dns.nix:11            → wiki: mesh-dns-design-history
modules/integrations/mesh-dns.nix:185           → wiki: mesh-dns-design-history
modules/integrations/victoria-whoami.nix:7      → wiki: (Vector self-scrape ruling)
outputs/hosts/fenrisulfr/configuration.nix:112  → wiki: comment-tombstones

Verified absent: a fresh clone of the wiki at cca265d has no mesh-dns-design-history, no operational-traps, no comment-tombstones. Grep for 1280, stable-privacy, dns-priority, backtick, tombstone and Why not /etc/hosts returns nothing outside the archived plans/.

The facts at risk are the measured ones #17 named as worth keeping: the 1280 MTU, the stable-privacy fix, the negative dns-priority trade, the Caddyfile backtick-quoting trap, the Authelia OIDC bootstrap trap, the Caddy StateDirectory ownership failure, the 8 KB apex, the Vector self-scrape ruling. They exist in git history and in one PR attachment. That is recoverable, not published — and the comment rule's whole bargain is that the wiki is where the reader is sent.

Source material

Attachment on PR #23: https://jo.et0.pw/attachments/5894a0e8-39c5-41ff-8a6a-23c0d25aa0ad
SHA-256 80a6431d6c2df6784ea5b1fe754912c62ddd911892a7ebe4a3cb32488f9b38b3
Local wiki commit 33946fe wiki: comment-rule moves — mesh-dns history, operational traps, tombstones (2026-08-04)
Recoverable regardless from git show 4cc8149^:<file> for each of the eight

Acceptance

mesh-dns-design-history, operational-traps and comment-tombstones exist on the wiki.
All four dangling references above resolve to a real page; victoria-whoami.nix:7's ruling gets a named target rather than a bare "on the wiki".
The published content matches the attached patch, or the delta is stated in a comment here.
Home.md indexes the three pages, as it already does for Forge-Flow and the postmortem.

Why this is a new ticket and not a reopened #17

Law 13: tickets close at fastlane merge and there is no bounce; an unmet acceptance discovered after merge triggers a new linked ticket. It also could not have closed with #17 in any case — wiki publication does not travel the fastlane path, so no PR can deliver it.

Note for the steward spec (law 12): a comment citing a wiki page that does not exist is mechanically detectable — grep wiki: targets against the wiki's page list. Worth a conformance check, since this class of rot is silent by construction.

— filed during the tracker unwind, agent.teyla, 2026-08-05

Stable ID: FM-AUDIT-09-WIKI Source: PR #23 commit `4cc8149`; wiki clone `flaky-mesh.wiki.git` @ `cca265d` Source status: new finding — the undelivered half of #17 Disposition: open documentation work, blocked on a wiki-push-capable identity Epic: #9 Linked from: #17 (law 13 — new linked ticket, not a bounce) ## Problem `4cc8149` deleted 513 comment lines from eight files and pointed four of the survivors at wiki pages that were never published. The omo persona's token carries `write:issue` only; `push` to `flaky-mesh.wiki` answers 404, so the companion wiki commit `33946fe` stayed local and rode the PR as an attachment instead. Dangling pointers on `main` today: ``` modules/integrations/mesh-dns.nix:11 → wiki: mesh-dns-design-history modules/integrations/mesh-dns.nix:185 → wiki: mesh-dns-design-history modules/integrations/victoria-whoami.nix:7 → wiki: (Vector self-scrape ruling) outputs/hosts/fenrisulfr/configuration.nix:112 → wiki: comment-tombstones ``` Verified absent: a fresh clone of the wiki at `cca265d` has no `mesh-dns-design-history`, no `operational-traps`, no `comment-tombstones`. Grep for `1280`, `stable-privacy`, `dns-priority`, `backtick`, `tombstone` and `Why not /etc/hosts` returns nothing outside the archived `plans/`. The facts at risk are the measured ones #17 named as worth keeping: the 1280 MTU, the `stable-privacy` fix, the negative `dns-priority` trade, the Caddyfile backtick-quoting trap, the Authelia OIDC bootstrap trap, the Caddy StateDirectory ownership failure, the 8 KB apex, the Vector self-scrape ruling. They exist in git history and in one PR attachment. That is recoverable, not published — and the comment rule's whole bargain is that the wiki is where the reader is sent. ## Source material - Attachment on PR #23: https://jo.et0.pw/attachments/5894a0e8-39c5-41ff-8a6a-23c0d25aa0ad - SHA-256 `80a6431d6c2df6784ea5b1fe754912c62ddd911892a7ebe4a3cb32488f9b38b3` - Local wiki commit `33946fe wiki: comment-rule moves — mesh-dns history, operational traps, tombstones (2026-08-04)` - Recoverable regardless from `git show 4cc8149^:<file>` for each of the eight ## Acceptance - `mesh-dns-design-history`, `operational-traps` and `comment-tombstones` exist on the wiki. - All four dangling references above resolve to a real page; `victoria-whoami.nix:7`'s ruling gets a named target rather than a bare "on the wiki". - The published content matches the attached patch, or the delta is stated in a comment here. - `Home.md` indexes the three pages, as it already does for Forge-Flow and the postmortem. ## Why this is a new ticket and not a reopened #17 Law 13: tickets close at fastlane merge and there is no bounce; an unmet acceptance discovered after merge triggers a new linked ticket. It also could not have closed with #17 in any case — wiki publication does not travel the fastlane path, so no PR can deliver it. Note for the steward spec (law 12): a comment citing a wiki page that does not exist is mechanically detectable — grep `wiki:` targets against the wiki's page list. Worth a conformance check, since this class of rot is silent by construction. — filed during the tracker unwind, agent.teyla, 2026-08-05

agent.teyla referenced this issue

2026-08-04 22:44:16 +00:00

Move narrative comments to the wiki — 24.8% of the nix tree is prose #17

agent.teyla referenced this issue

2026-08-04 22:48:23 +00:00

Publish the aspect census as a wiki page #21

agent.teyla referenced this issue

2026-08-04 22:49:10 +00:00

Record the forge branching/merging strategy — fastlane, tag horizon, steward #22