From 64bb23b32956df94934d1cae32dfbcae8b346111 Mon Sep 17 00:00:00 2001 From: Frank Date: Wed, 21 Oct 2026 02:40:59 -0700 Subject: [PATCH] docs(log): one dated section per day, and the sweep's lesson learned MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The day had three `## 2026-10-21` headings — three logs wearing one date, which is the sprawl the spec's one-dated-section rule exists to prevent. One date now, one `###` per campaign. `okf-maintenance.md` states the multi-campaign shape explicitly so nobody has to infer it, and names `AGENTS.md` as the co-owner of the entry law so an editor changes both. The new entry records what the dedupe sweep actually taught: an index that restates its own reference pages becomes the stale authority, and a subagent ledger is a claim until it is re-read against the file it accuses — most rows returned by the audit fan-out were checkably false, and half the ledgers never arrived at all. `skills/ecosystem.md` gains the `resource:` frontmatter the bundle's other externally-sourced pages carry. Refs #64 --- omp-docs/log.md | 41 ++++++++++++++++++++++++-- omp-docs/references/okf-maintenance.md | 5 +++- omp-docs/skills/ecosystem.md | 1 + 3 files changed, 43 insertions(+), 4 deletions(-) diff --git a/omp-docs/log.md b/omp-docs/log.md index 933debf..14e561c 100644 --- a/omp-docs/log.md +++ b/omp-docs/log.md @@ -22,7 +22,9 @@ not restated here — entry, then pointer. That is what the 2026-10-21 audit pas newest twelve entries: the facts stayed, the duplicates went, `git log --follow` keeps the long form. -## 2026-10-21 — reviewing a day of work, and finding checks that lie +## 2026-10-21 + +### reviewing a day of work, and finding checks that lie Two-axis review (Standards / Spec) of 51 commits, 30 findings, on `fix/60-review-findings`. Refs #60, merged PR #61. The findings were one shape: **a check that reports confidence it did @@ -55,7 +57,7 @@ exclusion list drifted apart, `.gitattributes` justified installing `git-lfs` fo that same week's diff untracked, and the one-log rule had four owners. A coverage claim names what was measured; a tool justified by dead config cannot survive the config. -## 2026-10-21 — an effort map folding against rejections that never existed +### an effort map folding against rejections that never existed Refs #62. `agent/models.yml` rewrote `minimal→low`, `high→xhigh`, `max→xhigh` for frank-dragoon to dodge 400s the engine does not send — flash-server's own error names its allow-list and the @@ -68,7 +70,7 @@ exactly its last capture** — settle it through a logging proxy, not by reading pass restored the three pre-callsign model ids the 2026-10-08 rename had overwritten inside its own explanatory comments. -## 2026-10-21 — a documented mode the panel never had +### a documented mode the panel never had The home ultrawide ran at 60 Hz for weeks because `desk-1-home.kdl` asked for `3440x1440@239.999` and the panel advertises `@239.998`. One character: niri matches mode @@ -81,6 +83,39 @@ at once (`wlr-randr` listed as installed while `pacman -Qs wlr` matches nothing) hardware, then destroy the stale copies. A correction is itself a measurement: this entry's first pass published a second wrong hardware fact, with a `verified:` date stamped on it. +### a dedupe sweep, and scouts whose ledgers did not survive contact with the files + +Refs #64. Owners moved, not words. The ghostty and Gitea indexes stopped carrying second copies of +the pages they route to — Gitea's index restated the container table, the boot-persistence law, the +management commands, and the data layout while its own See Also list named the four pages that own +them, and an index that restates an operational table becomes the second authority, which is the +one that goes stale. The llama.cpp overview handed Docker and the `LLAMA_ARG_*` rule back to the +setup page that had always promised them; the search finish rule has one owner again; fleet +hardware and the SearXNG engine count were re-read from the boxes rather than re-derived, and the +count is now stated as a size class because it moves weekly. + +Two laws no other page owns: + +- **A scout's ledger is a claim, not a finding.** The checkable-false share of the returned rows + was large: three pages "missing an H1" that have one; a 215-line `omp-docs/AGENTS.md` that does + not exist; a wikilink-and-wall defect in `core/settings.md` that a commit from that same morning + had already removed; `core/subagent-limits.md` called superseded while `agent/config.yml` still + carries `maxRecursionDepth: 1` and `maxRuntimeMs: 1800000` on the very lines the page cites. + Nothing entered the diff until it was re-read against the file it accused. +- **A ledger written to a file is not delivered.** One scout yielded against a zero-byte file; + three more wrote their path with the tool-call parameter block embedded in the filename, so their + ledgers exist under names no caller can ask for. Ask for the ledger as the yield text, then read + it before repeating it. + +Fan-out, measured the hard way: seven audit subagents on one local endpoint produced nothing for +seventeen minutes. `task.maxConcurrency` is 2, so five were queued while two thrashed, and +`proc://` labels a queued task `running` — which is not the claim it sounds like. Cancelling five +let the survivors land within minutes. + +The day's three `## 2026-10-21` sections are now one section with four subsections, which is what +the spec's one-dated-section-per-day rule always meant; [references/okf-maintenance.md](references/okf-maintenance.md) +says so explicitly now. + ## 2026-10-20 — one work log per bundle The bundle had two: this page and `core/log.md` — two entries of pure migration bookkeeping and diff --git a/omp-docs/references/okf-maintenance.md b/omp-docs/references/okf-maintenance.md index 2846550..3111e0b 100644 --- a/omp-docs/references/okf-maintenance.md +++ b/omp-docs/references/okf-maintenance.md @@ -49,7 +49,10 @@ Details: [secret gate](/tools/index.md). - **Link, do not duplicate.** Knowledge that outlives the entry belongs on its concept page; the entry points there. - **One dated section per day** (`## YYYY-MM-DD`), and mention `index.md` whenever a - file is added or removed. + file is added or removed. Several campaigns on one day share the section: a single + `##` date, one `###` per campaign — three `## 2026-10-21` headings is three logs + wearing one date. The entry law is also restated in the repo's `AGENTS.md` (the + always-loaded tier); change one, change the other. ### Common Mistakes diff --git a/omp-docs/skills/ecosystem.md b/omp-docs/skills/ecosystem.md index c785e51..53ea1ef 100644 --- a/omp-docs/skills/ecosystem.md +++ b/omp-docs/skills/ecosystem.md @@ -7,6 +7,7 @@ tags: - skills-sh - ecosystem - registry +resource: https://skills.sh timestamp: 2026-10-19 verified: 2026-10-19 ---