53259aebf1
Some checks are pending
CI / detect-changes (push) Waiting to run
CI / docs-check (push) Blocked by required conditions
CI / lint (push) Blocked by required conditions
CI / build (push) Blocked by required conditions
CI / integration-tests (push) Blocked by required conditions
CI / windows-portability (push) Blocked by required conditions
CI / rtk-portability (linux, blacksmith-4vcpu-ubuntu-2404) (push) Blocked by required conditions
CI / rtk-portability (macos, macos-15) (push) Blocked by required conditions
CI / rtk-portability (windows, blacksmith-4vcpu-windows-2025) (push) Blocked by required conditions
1. cooldown failover (sf-mp8w9cg9-arixq7, high) When a provider hits AUTH_COOLDOWN in unit execution, block the failing model with an expiry using the existing blockModel() API, then try a non-cooldowned provider via isProviderRequestReady. Only stops if every provider is unavailable, with an enumerated message showing which ones are down. loop.js consecutiveCooldowns is not touched here (it tracks the loop-level retry budget for provider-not-ready errors that bypass phases-unit; the cooldown path in loop.js is separate and handles errors thrown before runUnitPhase, while this fix handles cancellation returned from runUnitPhase due to provider error during session creation). 2. redundant reassess-roadmap on completed slices (sf-mp8wa4qr-xw8fjb, medium) Doctor-triggered reassess path (loop.js P4-A) now checks whether the target slice already has an ASSESSMENT file before queuing reassess-roadmap. Mirrors the guard already present in the normal dispatch path (checkNeedsReassessment). 3. empty structured fields in slice summary (sf-mp8w6s88-ckv4yr, low) Added explicit instruction in complete-slice.md prompt template directing the executor to derive key_files, key_decisions, and patterns_established from task summaries before calling complete_slice.
2.1 KiB
2.1 KiB
Records Keeper
The records keeper keeps repo memory ordered after meaningful changes. Run this checklist at milestone close, after architecture changes, after product behavior changes, and whenever docs/source disagree.
Use the records-keeper skill for this workflow when SF skills are available. Use context-doctor instead when stale state lives under .sf/ or the memory store.
Canonical Homes
- Root
AGENTS.md: short routing map for agents. ARCHITECTURE.md: short system map, boundaries, invariants, critical flows, and verification.docs/product-specs/: durable user-facing behavior and product decisions.docs/design-docs/: durable design and architecture decisions.docs/exec-plans/: active/completed work plans and technical debt.docs/generated/: generated references only.docs/records/: audits, ledgers, and context-gardening outputs.
Checklist
- Root map is current:
AGENTS.mdpoints to the right canonical docs and localAGENTS.mdfiles. - Architecture is current: new subsystems, boundaries, invariants, data/state, or critical flows are reflected in
ARCHITECTURE.md. - Product specs are current: user-visible behavior changes are reflected in
docs/product-specs/. - Execution plans are filed: active work is in
docs/exec-plans/active/; completed summaries and evidence are indocs/exec-plans/completed/. - Debt is visible: discovered cleanup is listed in
docs/exec-plans/tech-debt-tracker.md. - Generated docs are marked: generated material stays under
docs/generated/or clearly says how to regenerate it. - Contradictions are resolved: stale docs are updated or marked superseded with links to the source of truth.
- Verification is recorded: changed checks, evals, and commands are listed in the relevant plan or quality document.
Output
When records work is non-trivial, write a dated note under docs/records/ with:
- What changed.
- What canonical docs were updated.
- What contradictions were found.
- What remains unresolved.