From 411bc2ed60d3288c6547062ab5f8780c2b9af1b5 Mon Sep 17 00:00:00 2001 From: wshallwshall Date: Fri, 16 Oct 2026 10:47:21 -0500 Subject: [PATCH 1/8] wiki promotion: run the korus presence.ps1 by path for -Fleet The engine copy of presence.ps1 has no -Fleet parameter. Two seats measured it (wiki events 20261004T162651546Z-atc98r, 20261012T152837537Z-l477qc). --- roles/COMMON.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/roles/COMMON.md b/roles/COMMON.md index 1666657..4db558a 100644 --- a/roles/COMMON.md +++ b/roles/COMMON.md @@ -457,6 +457,10 @@ a seat that believes a lane is empty starts doing that lane's work. | Any claim about who can be MESSAGED | `list_sessions`, which is the other axis | | Either one, alone | Then say which axis you did not vary | +**Run korus's `presence.ps1` by path for `-Fleet`.** The engine copy has no `-Fleet` and refuses +it. Measured 2026-10-04 and 2026-10-12 (events `20261004T162651546Z-atc98r`, +`20261012T152837537Z-l477qc`). + **Say the scope beside the count.** "No Lander in this repo, at 17:30Z" is checkable. "There is no Lander" is a claim about a fleet you did not read. From c7d59482eab1d91ee473020dc83379a837bfdb48 Mon Sep 17 00:00:00 2001 From: Scott Hall Date: Fri, 16 Oct 2026 15:35:22 -0500 Subject: [PATCH 2/8] Apply the Lander's three replacement texts from the PR 228 review The Lander's review at 411bc2ed60 returned FIX. This commit applies its three replacement texts verbatim: - the new -Fleet paragraph in roles/COMMON.md, now naming the run, refs, wiki key and the empty-roster limit; - the COMMON.md "one exception" row, now "The exceptions", listing both; - roles/LANDER.md, which now points at the exceptions that row lists. --- roles/COMMON.md | 14 ++++++++++---- roles/LANDER.md | 2 +- 2 files changed, 11 insertions(+), 5 deletions(-) diff --git a/roles/COMMON.md b/roles/COMMON.md index 4db558a..0c0a128 100644 --- a/roles/COMMON.md +++ b/roles/COMMON.md @@ -171,7 +171,7 @@ your playbook. Never copy a literal path out of a document, because a stale path | What a Builder still releases | Its own claim on ALREADY-DONE, CONCLUDED-AS-RESEARCH and BLOCKED. None of the three opens a pull request, so nothing downstream ever fires. **This list is stated in three places; where they differ, this one governs.** | | `-Release` is worktree-scoped | It acts on the worktree your shell stands in. Releasing another worktree's claim needs `-Force`, and the script refuses first and probes the holder. Read the probe line; do not skip to `-Force`. | | Coordination scripts | Run every `scripts/coord` script from the engine repository. The vault holds no `fleet.ps1` or `mail.ps1`, and its `claim.ps1` is a stale copy. | -| The one exception, added 2026-09-24 | `alloc.ps1 -Kind backlog` runs in a vault checkout, because the ledger lives there. The engine's `alloc.ps1` takes only `-Kind adr` and refuses `backlog` at parameter binding. `roles/LANDER.md`, *7. Ledger discipline*, names where each ledger command runs. | +| The exceptions | `alloc.ps1 -Kind backlog` runs in a vault checkout, because the ledger lives there (added 2026-09-24). The engine's `alloc.ps1` takes only `-Kind adr` and refuses `backlog` at parameter binding. `presence.ps1 -Fleet` runs from a korus checkout by path, because the engine copy has no `-Fleet` (added 2026-10-16; see *You cannot write "there is no " from one roster*). `roles/LANDER.md`, *7. Ledger discipline*, names where each ledger command runs. | | Paths | List the directory. Never take a path out of a document. | | Relayed lists | Examine each open item before you relay a work list, and escalate when you are unsure. | | Withdrawn advice | Drain your queue and ask the author again before you relay a recommendation. | @@ -457,9 +457,15 @@ a seat that believes a lane is empty starts doing that lane's work. | Any claim about who can be MESSAGED | `list_sessions`, which is the other axis | | Either one, alone | Then say which axis you did not vary | -**Run korus's `presence.ps1` by path for `-Fleet`.** The engine copy has no `-Fleet` and refuses -it. Measured 2026-10-04 and 2026-10-12 (events `20261004T162651546Z-atc98r`, -`20261012T152837537Z-l477qc`). +**Run korus's `presence.ps1` by path for `-Fleet`, from a korus checkout at `origin/main`.** The +engine copy has no `-Fleet` and refuses it at parameter binding: + + pwsh -NoProfile -File /scripts/coord/presence.ps1 -Fleet + +The korus copy skips a session whose worktree is gone, where the engine copy refuses the all-clear. +So an empty `-Fleet` roster still does not prove a seat absent; say so beside the count. Run +2026-10-16 at engine `origin/main` `35f95e3f` and korus `origin/main` `468b571`. Wiki key +`coord/presence/fleet-flag`, event `20261012T152837537Z-l477qc`. **Say the scope beside the count.** "No Lander in this repo, at 17:30Z" is checkable. "There is no Lander" is a claim about a fleet you did not read. diff --git a/roles/LANDER.md b/roles/LANDER.md index e49c4f3..ed84f04 100644 --- a/roles/LANDER.md +++ b/roles/LANDER.md @@ -1305,7 +1305,7 @@ from 2026-07-24; the engine's is 781 lines. Read 2026-09-24: `claim.ps1 -List` showed 46 claims in the engine clone and 13 in the vault clone, most of the vault's marked STALE. *Coordination scripts* in [COMMON.md](COMMON.md) routes every -`scripts/coord` script to the engine, and backlog allocation is the one exception. +`scripts/coord` script to the engine, with the exceptions that row lists. **CORRECTED 2026-09-24.** This read *"Run every ledger command in this section in a vault checkout."* That sent claims to the wrong registry. A claim taken or released in the vault does From bad3d6cf72e9c316489fb4abae187575c847112a Mon Sep 17 00:00:00 2001 From: Scott Hall Date: Fri, 16 Oct 2026 15:39:58 -0500 Subject: [PATCH 3/8] Apply the Lander's shortened texts for PR 228 (round 2) The round-1 texts pushed two prose ratchets over baseline. This commit applies the Lander's shortened replacements verbatim: - roles/COMMON.md "Coordination scripts" row now defers to the next row; - "The exceptions" row is cut to the two exceptions; - the -Fleet paragraphs are cut, the command line unchanged; - roles/LANDER.md names *The exceptions* row as the place they are listed. --- roles/COMMON.md | 12 ++++-------- roles/LANDER.md | 3 +-- 2 files changed, 5 insertions(+), 10 deletions(-) diff --git a/roles/COMMON.md b/roles/COMMON.md index 0c0a128..eabea91 100644 --- a/roles/COMMON.md +++ b/roles/COMMON.md @@ -170,8 +170,8 @@ your playbook. Never copy a literal path out of a document, because a stale path | The one claim you do NOT release yourself | **A Builder's claim on work that will merge.** Since 2026-09-18 the **Lander** releases it, in the same act as the ledger update. | | What a Builder still releases | Its own claim on ALREADY-DONE, CONCLUDED-AS-RESEARCH and BLOCKED. None of the three opens a pull request, so nothing downstream ever fires. **This list is stated in three places; where they differ, this one governs.** | | `-Release` is worktree-scoped | It acts on the worktree your shell stands in. Releasing another worktree's claim needs `-Force`, and the script refuses first and probes the holder. Read the probe line; do not skip to `-Force`. | -| Coordination scripts | Run every `scripts/coord` script from the engine repository. The vault holds no `fleet.ps1` or `mail.ps1`, and its `claim.ps1` is a stale copy. | -| The exceptions | `alloc.ps1 -Kind backlog` runs in a vault checkout, because the ledger lives there (added 2026-09-24). The engine's `alloc.ps1` takes only `-Kind adr` and refuses `backlog` at parameter binding. `presence.ps1 -Fleet` runs from a korus checkout by path, because the engine copy has no `-Fleet` (added 2026-10-16; see *You cannot write "there is no " from one roster*). `roles/LANDER.md`, *7. Ledger discipline*, names where each ledger command runs. | +| Coordination scripts | Run `scripts/coord` scripts from the engine repository, except those the next row names. The vault holds no `fleet.ps1` or `mail.ps1`, and its `claim.ps1` is a stale copy. | +| The exceptions | `alloc.ps1 -Kind backlog` runs in a vault checkout, where the ledger lives; the engine's copy refuses it. `presence.ps1 -Fleet` runs by path from a korus checkout; the engine copy lacks `-Fleet`. | | Paths | List the directory. Never take a path out of a document. | | Relayed lists | Examine each open item before you relay a work list, and escalate when you are unsure. | | Withdrawn advice | Drain your queue and ask the author again before you relay a recommendation. | @@ -457,15 +457,11 @@ a seat that believes a lane is empty starts doing that lane's work. | Any claim about who can be MESSAGED | `list_sessions`, which is the other axis | | Either one, alone | Then say which axis you did not vary | -**Run korus's `presence.ps1` by path for `-Fleet`, from a korus checkout at `origin/main`.** The -engine copy has no `-Fleet` and refuses it at parameter binding: +**Run korus's `presence.ps1` by path for `-Fleet`.** The engine copy has no `-Fleet` and refuses it at parameter binding: pwsh -NoProfile -File /scripts/coord/presence.ps1 -Fleet -The korus copy skips a session whose worktree is gone, where the engine copy refuses the all-clear. -So an empty `-Fleet` roster still does not prove a seat absent; say so beside the count. Run -2026-10-16 at engine `origin/main` `35f95e3f` and korus `origin/main` `468b571`. Wiki key -`coord/presence/fleet-flag`, event `20261012T152837537Z-l477qc`. +An empty `-Fleet` roster still does not prove a seat absent: the korus copy drops a session whose worktree is gone, so say so beside the count. Read 2026-10-16 (engine `35f95e3f`, korus `468b571`); wiki key `coord/presence/fleet-flag`. **Say the scope beside the count.** "No Lander in this repo, at 17:30Z" is checkable. "There is no Lander" is a claim about a fleet you did not read. diff --git a/roles/LANDER.md b/roles/LANDER.md index ed84f04..12b158d 100644 --- a/roles/LANDER.md +++ b/roles/LANDER.md @@ -1304,8 +1304,7 @@ has issued ADR numbers since vault #1600, from its own records. Its `claim.ps1` from 2026-07-24; the engine's is 781 lines. Read 2026-09-24: `claim.ps1 -List` showed 46 claims in the engine clone and 13 in the vault clone, -most of the vault's marked STALE. *Coordination scripts* in [COMMON.md](COMMON.md) routes every -`scripts/coord` script to the engine, with the exceptions that row lists. +most of the vault's marked STALE. *Coordination scripts* in [COMMON.md](COMMON.md) routes `scripts/coord` scripts to the engine, and the row after it, *The exceptions*, names those that run elsewhere. **CORRECTED 2026-09-24.** This read *"Run every ledger command in this section in a vault checkout."* That sent claims to the wrong registry. A claim taken or released in the vault does From ad164b82aece2e1238ff0970ec803d50f0004186 Mon Sep 17 00:00:00 2001 From: Scott Hall Date: Fri, 16 Oct 2026 15:44:52 -0500 Subject: [PATCH 4/8] Apply the Lander's round-3 sentence swaps for PR 228 - roles/COMMON.md The exceptions row: -Kind adr stays in the engine. - The -Fleet lead sentence names a korus checkout current with origin/main. --- roles/COMMON.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/roles/COMMON.md b/roles/COMMON.md index eabea91..29d8af1 100644 --- a/roles/COMMON.md +++ b/roles/COMMON.md @@ -171,7 +171,7 @@ your playbook. Never copy a literal path out of a document, because a stale path | What a Builder still releases | Its own claim on ALREADY-DONE, CONCLUDED-AS-RESEARCH and BLOCKED. None of the three opens a pull request, so nothing downstream ever fires. **This list is stated in three places; where they differ, this one governs.** | | `-Release` is worktree-scoped | It acts on the worktree your shell stands in. Releasing another worktree's claim needs `-Force`, and the script refuses first and probes the holder. Read the probe line; do not skip to `-Force`. | | Coordination scripts | Run `scripts/coord` scripts from the engine repository, except those the next row names. The vault holds no `fleet.ps1` or `mail.ps1`, and its `claim.ps1` is a stale copy. | -| The exceptions | `alloc.ps1 -Kind backlog` runs in a vault checkout, where the ledger lives; the engine's copy refuses it. `presence.ps1 -Fleet` runs by path from a korus checkout; the engine copy lacks `-Fleet`. | +| The exceptions | `alloc.ps1 -Kind backlog` runs in a vault checkout, where the ledger lives; `-Kind adr` stays in the engine. `presence.ps1 -Fleet` runs by path from a korus checkout; the engine copy lacks `-Fleet`. | | Paths | List the directory. Never take a path out of a document. | | Relayed lists | Examine each open item before you relay a work list, and escalate when you are unsure. | | Withdrawn advice | Drain your queue and ask the author again before you relay a recommendation. | @@ -457,7 +457,7 @@ a seat that believes a lane is empty starts doing that lane's work. | Any claim about who can be MESSAGED | `list_sessions`, which is the other axis | | Either one, alone | Then say which axis you did not vary | -**Run korus's `presence.ps1` by path for `-Fleet`.** The engine copy has no `-Fleet` and refuses it at parameter binding: +**Run korus's `presence.ps1` by path for `-Fleet`, from a korus checkout current with `origin/main`.** The engine copy has no `-Fleet` and refuses it at parameter binding: pwsh -NoProfile -File /scripts/coord/presence.ps1 -Fleet From 81cd823389c2229e2624ab84f3ae4893889cd2fb Mon Sep 17 00:00:00 2001 From: Scott Hall Date: Fri, 16 Oct 2026 15:59:57 -0500 Subject: [PATCH 5/8] Apply the Lander's final-review texts for PR 228 (round 4) - roles/COMMON.md Coordination scripts row names The exceptions and LANDER.md section 7. - The exceptions row lists at least three, including vault-only usage-log.ps1. - The -Fleet lead carries the wiki key; the caveat cites presence.ps1 lines 191-193. - roles/LANDER.md says The exceptions names at least those that run elsewhere. --- roles/COMMON.md | 8 ++++---- roles/LANDER.md | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/roles/COMMON.md b/roles/COMMON.md index 29d8af1..84c2cca 100644 --- a/roles/COMMON.md +++ b/roles/COMMON.md @@ -170,8 +170,8 @@ your playbook. Never copy a literal path out of a document, because a stale path | The one claim you do NOT release yourself | **A Builder's claim on work that will merge.** Since 2026-09-18 the **Lander** releases it, in the same act as the ledger update. | | What a Builder still releases | Its own claim on ALREADY-DONE, CONCLUDED-AS-RESEARCH and BLOCKED. None of the three opens a pull request, so nothing downstream ever fires. **This list is stated in three places; where they differ, this one governs.** | | `-Release` is worktree-scoped | It acts on the worktree your shell stands in. Releasing another worktree's claim needs `-Force`, and the script refuses first and probes the holder. Read the probe line; do not skip to `-Force`. | -| Coordination scripts | Run `scripts/coord` scripts from the engine repository, except those the next row names. The vault holds no `fleet.ps1` or `mail.ps1`, and its `claim.ps1` is a stale copy. | -| The exceptions | `alloc.ps1 -Kind backlog` runs in a vault checkout, where the ledger lives; `-Kind adr` stays in the engine. `presence.ps1 -Fleet` runs by path from a korus checkout; the engine copy lacks `-Fleet`. | +| Coordination scripts | Run `scripts/coord` scripts from the engine repository, except those *The exceptions* names; LANDER.md section 7 names where each ledger command runs. The vault holds no `fleet.ps1` or `mail.ps1`, and its `claim.ps1` is a stale copy. | +| The exceptions | At least: `alloc.ps1 -Kind backlog` in a vault checkout, since the engine's copy refuses it (added 2026-09-24; `-Kind adr` stays in the engine); vault-only `usage-log.ps1`; `presence.ps1 -Fleet` by path from korus. | | Paths | List the directory. Never take a path out of a document. | | Relayed lists | Examine each open item before you relay a work list, and escalate when you are unsure. | | Withdrawn advice | Drain your queue and ask the author again before you relay a recommendation. | @@ -457,11 +457,11 @@ a seat that believes a lane is empty starts doing that lane's work. | Any claim about who can be MESSAGED | `list_sessions`, which is the other axis | | Either one, alone | Then say which axis you did not vary | -**Run korus's `presence.ps1` by path for `-Fleet`, from a korus checkout current with `origin/main`.** The engine copy has no `-Fleet` and refuses it at parameter binding: +**Run korus's `presence.ps1` by path for `-Fleet`, from a korus checkout current with `origin/main`.** The engine copy has no `-Fleet` and refuses it at parameter binding (wiki key `coord/presence/fleet-flag`): pwsh -NoProfile -File /scripts/coord/presence.ps1 -Fleet -An empty `-Fleet` roster still does not prove a seat absent: the korus copy drops a session whose worktree is gone, so say so beside the count. Read 2026-10-16 (engine `35f95e3f`, korus `468b571`); wiki key `coord/presence/fleet-flag`. +A `-Fleet` roster without a seat does not prove it absent: the korus copy skips any session whose cwd is gone or outside a git repository (`presence.ps1` lines 191-193, korus `ad164b8`, read 2026-10-16). Say so beside the count. **Say the scope beside the count.** "No Lander in this repo, at 17:30Z" is checkable. "There is no Lander" is a claim about a fleet you did not read. diff --git a/roles/LANDER.md b/roles/LANDER.md index 12b158d..4c4d37c 100644 --- a/roles/LANDER.md +++ b/roles/LANDER.md @@ -1304,7 +1304,7 @@ has issued ADR numbers since vault #1600, from its own records. Its `claim.ps1` from 2026-07-24; the engine's is 781 lines. Read 2026-09-24: `claim.ps1 -List` showed 46 claims in the engine clone and 13 in the vault clone, -most of the vault's marked STALE. *Coordination scripts* in [COMMON.md](COMMON.md) routes `scripts/coord` scripts to the engine, and the row after it, *The exceptions*, names those that run elsewhere. +most of the vault's marked STALE. *Coordination scripts* in [COMMON.md](COMMON.md) routes `scripts/coord` scripts to the engine, and *The exceptions* names at least those that run elsewhere. **CORRECTED 2026-09-24.** This read *"Run every ledger command in this section in a vault checkout."* That sent claims to the wrong registry. A claim taken or released in the vault does From f84a4c736a1658043b50ce3bf9c6c50daecb6a08 Mon Sep 17 00:00:00 2001 From: Scott Hall Date: Fri, 16 Oct 2026 16:01:46 -0500 Subject: [PATCH 6/8] Split the -Fleet caveat sentence for PR 228 (round 5) The caveat now says the korus copy drops a session's repository from its scan, and splits one 33-word sentence so the long-sentence ratchet holds. --- roles/COMMON.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/COMMON.md b/roles/COMMON.md index 84c2cca..af3ac75 100644 --- a/roles/COMMON.md +++ b/roles/COMMON.md @@ -461,7 +461,7 @@ a seat that believes a lane is empty starts doing that lane's work. pwsh -NoProfile -File /scripts/coord/presence.ps1 -Fleet -A `-Fleet` roster without a seat does not prove it absent: the korus copy skips any session whose cwd is gone or outside a git repository (`presence.ps1` lines 191-193, korus `ad164b8`, read 2026-10-16). Say so beside the count. +A `-Fleet` roster without a seat does not prove it absent. The korus copy drops from its scan the repository of any session whose cwd is gone or outside a git repository (`presence.ps1` lines 191-193, korus `ad164b8`, read 2026-10-16). Say so beside the count. **Say the scope beside the count.** "No Lander in this repo, at 17:30Z" is checkable. "There is no Lander" is a claim about a fleet you did not read. From 115d6d1ec5ff469bb4504997d4dca0418b47a523 Mon Sep 17 00:00:00 2001 From: Scott Hall Date: Fri, 16 Oct 2026 16:15:21 -0500 Subject: [PATCH 7/8] Apply the Lander's round-6 texts for PR 228 - roles/COMMON.md -Fleet caveat says which repositories the scan skips. - Coordination scripts and The exceptions rows say at least some. - roles/LANDER.md says The exceptions names at least some of them. --- roles/COMMON.md | 6 +++--- roles/LANDER.md | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/roles/COMMON.md b/roles/COMMON.md index af3ac75..4544c04 100644 --- a/roles/COMMON.md +++ b/roles/COMMON.md @@ -170,8 +170,8 @@ your playbook. Never copy a literal path out of a document, because a stale path | The one claim you do NOT release yourself | **A Builder's claim on work that will merge.** Since 2026-09-18 the **Lander** releases it, in the same act as the ledger update. | | What a Builder still releases | Its own claim on ALREADY-DONE, CONCLUDED-AS-RESEARCH and BLOCKED. None of the three opens a pull request, so nothing downstream ever fires. **This list is stated in three places; where they differ, this one governs.** | | `-Release` is worktree-scoped | It acts on the worktree your shell stands in. Releasing another worktree's claim needs `-Force`, and the script refuses first and probes the holder. Read the probe line; do not skip to `-Force`. | -| Coordination scripts | Run `scripts/coord` scripts from the engine repository, except those *The exceptions* names; LANDER.md section 7 names where each ledger command runs. The vault holds no `fleet.ps1` or `mail.ps1`, and its `claim.ps1` is a stale copy. | -| The exceptions | At least: `alloc.ps1 -Kind backlog` in a vault checkout, since the engine's copy refuses it (added 2026-09-24; `-Kind adr` stays in the engine); vault-only `usage-log.ps1`; `presence.ps1 -Fleet` by path from korus. | +| Coordination scripts | Run `scripts/coord` scripts from the engine, except those living elsewhere (*The exceptions* names at least some; LANDER.md *7. Ledger discipline* covers ledger commands). The vault lacks `fleet.ps1` and `mail.ps1`; its `claim.ps1` is stale. | +| The exceptions | At least: `alloc.ps1 -Kind backlog` in a vault checkout, since the engine's copy refuses it (`-Kind adr` stays in the engine); vault-only `usage-log.ps1`; `presence.ps1 -Fleet` by path from a korus checkout. This row was added 2026-09-24. | | Paths | List the directory. Never take a path out of a document. | | Relayed lists | Examine each open item before you relay a work list, and escalate when you are unsure. | | Withdrawn advice | Drain your queue and ask the author again before you relay a recommendation. | @@ -461,7 +461,7 @@ a seat that believes a lane is empty starts doing that lane's work. pwsh -NoProfile -File /scripts/coord/presence.ps1 -Fleet -A `-Fleet` roster without a seat does not prove it absent. The korus copy drops from its scan the repository of any session whose cwd is gone or outside a git repository (`presence.ps1` lines 191-193, korus `ad164b8`, read 2026-10-16). Say so beside the count. +A `-Fleet` roster without a seat does not prove the seat absent. The korus copy picks repositories from session cwds and skips a cwd that is gone or outside git (`presence.ps1` lines 191-193, korus `468b571`, read 2026-10-16). It scans no repository that no session's cwd resolves into. **Say the scope beside the count.** "No Lander in this repo, at 17:30Z" is checkable. "There is no Lander" is a claim about a fleet you did not read. diff --git a/roles/LANDER.md b/roles/LANDER.md index 4c4d37c..183450d 100644 --- a/roles/LANDER.md +++ b/roles/LANDER.md @@ -1304,7 +1304,7 @@ has issued ADR numbers since vault #1600, from its own records. Its `claim.ps1` from 2026-07-24; the engine's is 781 lines. Read 2026-09-24: `claim.ps1 -List` showed 46 claims in the engine clone and 13 in the vault clone, -most of the vault's marked STALE. *Coordination scripts* in [COMMON.md](COMMON.md) routes `scripts/coord` scripts to the engine, and *The exceptions* names at least those that run elsewhere. +most of the vault's marked STALE. *Coordination scripts* in [COMMON.md](COMMON.md) routes `scripts/coord` scripts to the engine, and *The exceptions* names at least some of those that run elsewhere. **CORRECTED 2026-09-24.** This read *"Run every ledger command in this section in a vault checkout."* That sent claims to the wrong registry. A claim taken or released in the vault does From 09619830dc2edb1472e3bc59b70c4377ffbeff17 Mon Sep 17 00:00:00 2001 From: Scott Hall Date: Fri, 16 Oct 2026 16:26:22 -0500 Subject: [PATCH 8/8] Apply the Lander's round-7 texts for PR 228 - roles/COMMON.md -Fleet caveat names the line-199 fallback to the caller's repository. - The exceptions row dates only the alloc.ps1 entry to 2026-09-24. --- roles/COMMON.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/roles/COMMON.md b/roles/COMMON.md index 4544c04..70b354b 100644 --- a/roles/COMMON.md +++ b/roles/COMMON.md @@ -171,7 +171,7 @@ your playbook. Never copy a literal path out of a document, because a stale path | What a Builder still releases | Its own claim on ALREADY-DONE, CONCLUDED-AS-RESEARCH and BLOCKED. None of the three opens a pull request, so nothing downstream ever fires. **This list is stated in three places; where they differ, this one governs.** | | `-Release` is worktree-scoped | It acts on the worktree your shell stands in. Releasing another worktree's claim needs `-Force`, and the script refuses first and probes the holder. Read the probe line; do not skip to `-Force`. | | Coordination scripts | Run `scripts/coord` scripts from the engine, except those living elsewhere (*The exceptions* names at least some; LANDER.md *7. Ledger discipline* covers ledger commands). The vault lacks `fleet.ps1` and `mail.ps1`; its `claim.ps1` is stale. | -| The exceptions | At least: `alloc.ps1 -Kind backlog` in a vault checkout, since the engine's copy refuses it (`-Kind adr` stays in the engine); vault-only `usage-log.ps1`; `presence.ps1 -Fleet` by path from a korus checkout. This row was added 2026-09-24. | +| The exceptions | At least: `alloc.ps1 -Kind backlog` in a vault checkout, since the engine's copy refuses it (`-Kind adr` stays in the engine); vault-only `usage-log.ps1`; `presence.ps1 -Fleet` by path from a korus checkout. The `alloc.ps1` entry was added 2026-09-24. | | Paths | List the directory. Never take a path out of a document. | | Relayed lists | Examine each open item before you relay a work list, and escalate when you are unsure. | | Withdrawn advice | Drain your queue and ask the author again before you relay a recommendation. | @@ -461,7 +461,7 @@ a seat that believes a lane is empty starts doing that lane's work. pwsh -NoProfile -File /scripts/coord/presence.ps1 -Fleet -A `-Fleet` roster without a seat does not prove the seat absent. The korus copy picks repositories from session cwds and skips a cwd that is gone or outside git (`presence.ps1` lines 191-193, korus `468b571`, read 2026-10-16). It scans no repository that no session's cwd resolves into. +A `-Fleet` roster without a seat does not prove the seat absent. The korus copy picks repositories from session cwds and skips a cwd that is gone or outside git (`presence.ps1` lines 191-193, korus `468b571`, read 2026-10-16). If no cwd is usable, it scans the caller's repository (line 199). **Say the scope beside the count.** "No Lander in this repo, at 17:30Z" is checkable. "There is no Lander" is a claim about a fleet you did not read.