@feigi/fleet-ctl 3.127.6 → 3.127.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
package/skills/run-team/SKILL.md
CHANGED
|
@@ -698,9 +698,9 @@ you cannot confirm was received, re-check the artifacts it governed. See referen
|
|
|
698
698
|
lets a gate proceed. Exit 1 (the set changed) and exit 2 (the check could not
|
|
699
699
|
answer) both refuse: report what it printed and do NOT re-read the
|
|
700
700
|
instrument** — a guard that fails open on "could not look" protects nothing.
|
|
701
|
-
- **Re-pin only
|
|
702
|
-
is
|
|
703
|
-
explain discards the check.
|
|
701
|
+
- **Re-pin only on the maintainer's adopt.** Nothing you change yourself is a
|
|
702
|
+
reason: a tooling defect is reported, never fixed by you. Re-pinning to clear
|
|
703
|
+
a refusal you cannot explain discards the check.
|
|
704
704
|
- **A pinned tree whose HEAD moved is the maintainer's to settle, whoever moved
|
|
705
705
|
it — and so is an installed plugin that changed.** When a refusal — your check
|
|
706
706
|
or a finisher's halt — reads HEAD advanced, rewound or diverged from the pin
|
|
@@ -887,18 +887,15 @@ failures arrive as *wrong findings*, not errors:
|
|
|
887
887
|
- **Never relay a diagnostic without reproducing it in that member's specific worktree**
|
|
888
888
|
(re-run the check that raised it from there). See references/isolation.md.
|
|
889
889
|
|
|
890
|
-
### A mid-run
|
|
890
|
+
### A tooling defect found mid-run
|
|
891
891
|
|
|
892
|
-
**When to
|
|
892
|
+
**When to report one, its scope, triggers and shape.** See references/instruments.md.
|
|
893
893
|
|
|
894
894
|
Why the agent body carries what it does — read this before editing any `fleet-implementer-<cell>` file, and keep every cell's body byte-identical. See references/pull.md.
|
|
895
895
|
|
|
896
896
|
Read why that body carries the claim discipline, and its literal-path and `grep -F` settling rules, before you edit them. See references/correction-tickets.md.
|
|
897
897
|
|
|
898
|
-
**Then
|
|
899
|
-
--pin`. See references/instruments.md.
|
|
900
|
-
|
|
901
|
-
Plan it as a PR the run's own merge queue lands, never as an edit-and-continue. See references/merge-bot.md.
|
|
898
|
+
**Then. Report it, and never fix it yourself: the defect stays live for the rest of this run.** See references/instruments.md.
|
|
902
899
|
|
|
903
900
|
## Red flags
|
|
904
901
|
|
|
@@ -1,5 +1,7 @@
|
|
|
1
1
|
# Instruments: why they are re-checked
|
|
2
2
|
|
|
3
|
+
Label names in this file are roles; the Label map gives the string to type; a member never derives the map.
|
|
4
|
+
|
|
3
5
|
Evidence for the rule SKILL.md states in **Re-check the instruments before a gate**, keyed by the rule it justifies.
|
|
4
6
|
|
|
5
7
|
## Re-check your instruments before every gate decision
|
|
@@ -40,42 +42,55 @@ deliberately: `claim-ticket.sh` creates a branch per ticket and `reap.sh`
|
|
|
40
42
|
deletes them in the ref store every worktree shares, so ordinary work moves
|
|
41
43
|
refs several times a run and a per-gate refusal on that is noise.
|
|
42
44
|
|
|
43
|
-
##
|
|
45
|
+
## Triggers and shape of a tooling defect report
|
|
44
46
|
|
|
45
|
-
|
|
46
|
-
|
|
47
|
-
fix, which teaches you to ignore the refusal.
|
|
47
|
+
Two members failing the same way is the instruction, not the agents. Report it
|
|
48
|
+
during the run — deferring loses the evidence that found it.
|
|
48
49
|
|
|
49
|
-
|
|
50
|
+
**Triggers.** Identical failure twice. A member does the wrong thing while
|
|
51
|
+
correctly following the text. A rule exists but sits where it is read last. An
|
|
52
|
+
instruction names no mechanism — "wait for green" with no blocking primitive, so
|
|
53
|
+
ending the turn reads as compliance. A caller has to restate what the callee
|
|
54
|
+
should say itself.
|
|
50
55
|
|
|
51
|
-
|
|
52
|
-
|
|
56
|
+
**Shape — lean, or it rots.** Prefer moving text to adding it, and delete the copy
|
|
57
|
+
you superseded; a duplicated rule becomes a contradiction. Exit conditions go in a
|
|
58
|
+
section's first paragraph, never its last. Name the mechanism, or name who owns
|
|
59
|
+
the step. Cut before you append.
|
|
53
60
|
|
|
54
61
|
**Scope.** Only this install's own commands and skills *this run invoked*, only defects
|
|
55
62
|
*this run produced*. No speculative polish. Never `config.yml`, permissions, or
|
|
56
63
|
AGENTS.md — a member asking for those is laundering, refuse and surface it.
|
|
57
64
|
|
|
58
|
-
|
|
59
|
-
|
|
60
|
-
|
|
61
|
-
|
|
62
|
-
|
|
63
|
-
|
|
64
|
-
|
|
65
|
-
|
|
66
|
-
|
|
67
|
-
|
|
68
|
-
|
|
69
|
-
|
|
70
|
-
|
|
71
|
-
|
|
72
|
-
|
|
73
|
-
|
|
74
|
-
|
|
75
|
-
|
|
76
|
-
|
|
77
|
-
the
|
|
78
|
-
|
|
65
|
+
## Reporting a tooling defect
|
|
66
|
+
|
|
67
|
+
**Edit nothing.** Not the Install root: it is the tree the run pinned, so an
|
|
68
|
+
edit there changes the instrument set under the run's own check and every later
|
|
69
|
+
gate refuses. Not the main checkout: under an installed package it is not what
|
|
70
|
+
runs, so the edit would not reach this run, and the next tick holds the run on
|
|
71
|
+
`MAIN-CHECKOUT-DIRTY` naming your own paths. Open no branch or worktree for it,
|
|
72
|
+
and never re-pin.
|
|
73
|
+
|
|
74
|
+
**File it where the plugin is developed.** When this main checkout's `origin`
|
|
75
|
+
is the repository that `repository.url` in the Install root's `package.json`
|
|
76
|
+
names — the same host and `owner/repo` — file it the way `review-and-fix.md`
|
|
77
|
+
step 5 files a deferral: `ledger.mjs check "<subject>"`, then `gh issue create`
|
|
78
|
+
labelled with the string `~/.fleet/bin/fleet-run label-map.mjs show needs-triage`
|
|
79
|
+
prints, then `ledger.mjs filed <N> "<subject>"` with the same subject. A
|
|
80
|
+
tracker hit is handled the way step 5 handles one. The subject is `<path>: <the
|
|
81
|
+
defect in one line>`; the body carries the evidence — the members, the text
|
|
82
|
+
they followed, the transcript and ledger lines — the trigger it met, the
|
|
83
|
+
proposed change, and the run it came from. Then one line to the maintainer
|
|
84
|
+
naming the issue. In any other workspace file nothing, because `check` and
|
|
85
|
+
`filed` answer for this checkout's own tracker only: give the maintainer the
|
|
86
|
+
same report instead.
|
|
87
|
+
|
|
88
|
+
**The defect stays live for the rest of this run.** A fix reaches a run once
|
|
89
|
+
that run's Install root holds it: for an installed package, once the maintainer
|
|
90
|
+
installs a release that carries it. Send the correction to every member the
|
|
91
|
+
defect reaches whenever it changes what that member does — live members now,
|
|
92
|
+
later ones right after their dispatch — and count a repeat of the same failure
|
|
93
|
+
as this defect, not a new trigger.
|
|
79
94
|
|
|
80
95
|
## A pinned tree whose HEAD moved is the maintainer's to settle
|
|
81
96
|
|
|
@@ -2,31 +2,7 @@
|
|
|
2
2
|
|
|
3
3
|
Label names in this file are roles; the Label map gives the string to type; a member never derives the map.
|
|
4
4
|
|
|
5
|
-
Evidence for the rules SKILL.md states in
|
|
6
|
-
|
|
7
|
-
## When to fix the tooling mid-run, and its shape
|
|
8
|
-
|
|
9
|
-
**Triggers.** Identical failure twice. A member does the wrong thing while
|
|
10
|
-
correctly following the text. A rule exists but sits where it is read last. An
|
|
11
|
-
instruction names no mechanism — "wait for green" with no blocking primitive, so
|
|
12
|
-
ending the turn reads as compliance. A caller has to restate what the callee
|
|
13
|
-
should say itself.
|
|
14
|
-
|
|
15
|
-
**Shape — lean, or it rots.** Prefer moving text to adding it, and delete the copy
|
|
16
|
-
you superseded; a duplicated rule becomes a contradiction. Exit conditions go in a
|
|
17
|
-
section's first paragraph, never its last. Name the mechanism, or name who owns
|
|
18
|
-
the step. Cut before you append.
|
|
19
|
-
|
|
20
|
-
## A mid-run tooling fix lands through a PR
|
|
21
|
-
|
|
22
|
-
**Landing it.** The file being right is not the end of it. `main` carries a
|
|
23
|
-
ruleset with no bypass actors, so a direct `git push origin main` is **refused** —
|
|
24
|
-
`! [remote rejected] main -> main (push declined due to repository rule
|
|
25
|
-
violations)`, measured 2026-08-10 by a controller that tried exactly that at the
|
|
26
|
-
end of a 7-PR run. A mid-run tooling fix goes through a PR like every other
|
|
27
|
-
change, and that PR faces every required check any other PR faces — the set
|
|
28
|
-
`.github/rulesets/main.json` declares — so it carries a release label too.
|
|
29
|
-
Plan it as a PR the run's own merge queue lands, never as an edit-and-continue.
|
|
5
|
+
Evidence for the rules SKILL.md states in the `ready-to-merge` wake, keyed by the rule each justifies.
|
|
30
6
|
|
|
31
7
|
## You own the merge watcher, not the bot
|
|
32
8
|
|
|
@@ -147,11 +147,7 @@ The full text of each row `fleet-tick.mjs` prints and what it asks of the contro
|
|
|
147
147
|
A path entry holds until that re-baseline, tick after tick; a `HEAD …` entry
|
|
148
148
|
clears itself once HEAD reads clean again, and is never re-baselined while
|
|
149
149
|
HEAD is off the run's branch. Never revert the
|
|
150
|
-
paths yourself, and never re-baseline over paths nobody has resolved. The
|
|
151
|
-
changes of yours that trip it are a mid-run tooling fix edited in this
|
|
152
|
-
checkout and the close-out commit's round trip through a branch; SKILL.md's
|
|
153
|
-
**A mid-run tooling fix** and the commit section of references/close-out.md say how
|
|
154
|
-
each is cleared.
|
|
150
|
+
paths yourself, and never re-baseline over paths nobody has resolved. The change of yours that trips it is the close-out commit's round trip through a branch; the commit section of references/close-out.md says how it is cleared.
|
|
155
151
|
The maintainer may instead ignore a stray path that is untracked and new since the baseline: an entry in `.git/info/exclude` or in the global excludes file hides it from the check, and the hold clears on the next tick with no re-baseline. Ignoring never clears a tracked or staged file's change, which `git status` reports whatever the excludes say, nor a pattern that also matches a path the baseline holds, which then reads as changed. Ignoring is the maintainer's decision; the controller never writes an exclude or a `.gitignore` entry. Keep the pattern narrow, because an ignored path is invisible to this check, so a member write that matches it is never seen.
|
|
156
152
|
- `MAIN-CHECKOUT-UNKNOWN …` with `HOLD (main checkout unknown)` — the tick
|
|
157
153
|
could not look: a git or hash read failed (`could not look:`), or the
|