Align scheduler docs to cmdCheck excluded schema

This commit is contained in:
thePR0M3TH3AN committed 2026-02-14 15:53:18 -05:00
1 parent f3020f9e3c
commit e8ff52cc57
2 files changed
+9 -3

No files matched your search

+4 -2
View File
@@ -21,7 +21,8 @@ MUST 2: Run preflight to get the exclusion set:
npm run lock:check:daily
Use the `locked` array from the JSON output as the exclusion set.
Use `excluded` from the JSON output as the canonical exclusion set.
If `excluded` is unavailable, fallback to the union of `locked`, `paused`, and `completed`.
MUST 3: Run these commands in this order:
1) test -f AGENTS.md && cat AGENTS.md || echo "No AGENTS.md found; continuing" (missing AGENTS.md is non-fatal)
@@ -83,7 +84,8 @@ MUST 2: Run preflight to get the exclusion set:
npm run lock:check:weekly
Use the `locked` array from the JSON output as the exclusion set.
Use `excluded` from the JSON output as the canonical exclusion set.
If `excluded` is unavailable, fallback to the union of `locked`, `paused`, and `completed`.
MUST 3: Run these commands in this order:
1) test -f AGENTS.md && cat AGENTS.md || echo "No AGENTS.md found; continuing" (missing AGENTS.md is non-fatal)
+5 -1
View File
@@ -16,6 +16,10 @@ Use this document for all scheduler runs.
if daily: `npm run lock:check:daily`; if weekly: `npm run lock:check:weekly`
```
Canonical exclusion rule:
- Use `excluded` from the `npm run lock:check:<cadence>` JSON output.
- If `excluded` is unavailable, fallback to the union of `locked`, `paused`, and `completed` from that same JSON payload.
3. Read policy file(s). This step is conditional: if `AGENTS.md` is missing, continue without failing.
```bash
@@ -37,7 +41,7 @@ Use this document for all scheduler runs.
Selection algorithm (MUST be followed exactly):
- Roster source: `src/prompts/roster.json` and the key matching `<cadence>`.
- Let `roster` be that ordered array and `excluded` be the `excluded` set (including paused and locked agents) from the JSON output of step 2.
- Let `roster` be that ordered array and `excluded` be the set from step 2's canonical exclusion rule.
- Let `latest_file` be the lexicographically last filename in `<log_dir>`.
- Determine `previous_agent` from `latest_file` using this precedence:
1. Parse YAML frontmatter from `<log_dir>/<latest_file>` and use key `agent` when present and non-empty.