@feigi/fleet-ctl 3.134.0 → 3.135.0

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
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@feigi/fleet-ctl",
3
- "version": "3.134.0",
3
+ "version": "3.135.0",
4
4
  "description": "Agent fleet: run-team controller, merge bot, PR reviewer, and the ticket pipeline they share",
5
5
  "license": "Apache-2.0",
6
6
  "repository": {
@@ -25,9 +25,11 @@
25
25
  //
26
26
  // prose isDocs() calls it docs, it ends in .md or .markdown, it is not
27
27
  // under a test directory, and it is outside the prompt surface: no
28
- // directory segment named skills, agents, commands or plugin, no
29
- // directory segment that starts with a dot, and no file named
30
- // AGENTS.md, CLAUDE.md or GEMINI.md, at any depth
28
+ // directory segment named skills, agents or commands, no directory
29
+ // segment that starts with a dot, and no file named AGENTS.md,
30
+ // CLAUDE.md or GEMINI.md, at any depth. A file directly in the root
31
+ // .out-of-scope/, spelled exactly so, is exempt from the dot rule
32
+ // alone
31
33
  // data one of the METRICS paths closeout.mjs names, and no other file
32
34
  //
33
35
  // Stdout is one JSON line:
@@ -69,7 +71,8 @@ const ZERO = "000000";
69
71
  const PLAIN = "100644";
70
72
  const SHA = /^[0-9a-f]{40}$/;
71
73
  const RAW = /^:(\d{6}) (\d{6}) ([0-9a-f]+) ([0-9a-f]+) (\S+)$/;
72
- const PROMPT_DIRS = new Set(["skills", "agents", "commands", "plugin"]);
74
+ const PROMPT_DIRS = new Set(["skills", "agents", "commands"]);
75
+ const RECORDS_DIR = ".out-of-scope";
73
76
  const PROMPT_FILES = new Set(["agents.md", "claude.md", "gemini.md"]);
74
77
  const USAGE = "usage: finisher-scope.mjs --worktree <abs-path> --pin <sha> [--repo <dir>]";
75
78
  const EXIT = { inert: 0, "not-inert": 1, unknown: 2 };
@@ -110,10 +113,16 @@ function modeProblem(status, oldMode, newMode) {
110
113
  // is where omp and the tools it discovers keep what they load as instructions
111
114
  // (`.omp/rules`, `.omp/RULES.md`, `.omp/SYSTEM.md`, `.claude`, `.cursor`,
112
115
  // `.github/copilot-instructions.md`), so every one is the prompt surface
113
- // rather than a list of them that drifts as discovery grows.
116
+ // rather than a list of them that drifts as discovery grows. The one exception
117
+ // is a file directly in the root `.out-of-scope/`: the triage skill writes a
118
+ // rejection record there, read as settled precedent rather than as an
119
+ // instruction, so the directory rule passes over it. Nested, elsewhere or
120
+ // spelled otherwise, it is a dot-directory like any other, and the file-name
121
+ // rule still applies.
114
122
  function promptSurface(path) {
115
123
  const parts = path.split("/");
116
- for (const dir of parts.slice(0, -1)) {
124
+ const dirs = parts.length === 2 && parts[0] === RECORDS_DIR ? [] : parts.slice(0, -1);
125
+ for (const dir of dirs) {
117
126
  if (dir.startsWith(".") || PROMPT_DIRS.has(dir.toLowerCase())) return `prompt surface: directory ${dir}`;
118
127
  }
119
128
  const file = parts.at(-1).toLowerCase();
@@ -226,10 +226,14 @@ prompt surface) or only of the run-metrics files. The finisher does not decide
226
226
  that by reading the diff: the script reads it, and only its exit 0 skips the
227
227
  mutation. An exit 1 is not overridden, and an exit 2 is never read as a 0.
228
228
 
229
- The prompt surface stays out of prose. A `.md` under a `skills`, `agents`,
230
- `commands` or `plugin` directory or under any dot-directory (`.omp/rules`,
229
+ The prompt surface stays out of prose. A `.md` under a `skills`, `agents` or
230
+ `commands` directory or under any dot-directory (`.omp/rules`,
231
231
  `.omp/RULES.md`, `.claude`), and any `AGENTS.md`, `CLAUDE.md` or `GEMINI.md`, is
232
- read by the harness, so it can change behavior. A symlink, submodule, mode
232
+ read by the harness, so it can change behavior. The one exception is a file
233
+ directly in the root `.out-of-scope/`, spelled exactly so: a rejection record
234
+ the triage skill writes, read as settled precedent, so it is prose unless it is
235
+ named `AGENTS.md`, `CLAUDE.md` or `GEMINI.md`. Nested or elsewhere,
236
+ `.out-of-scope` is a dot-directory like any other. A symlink, submodule, mode
233
237
  change or other non-regular entry is a code change whatever its name, so it is
234
238
  not prose either. The verdict is read at the dispatch pin: the worktree's own
235
239
  head is not part of it, and duty 1 audits that head separately.