Repository navigation
docs: sync learn-cron-dashboard spec with main - #40010
Conversation
First Principles Review (Opus 5.5) — ⏭️ skippedRevision |
UX Review (Opus 5.5) — ⏭️ skippedRevision |
Opus 5.5 Review — ✅ no blocking findingsReviewed Verdict parsed from the review's SHA-scoped output markers for commit False positive or not applicable? A repository writer can comment: |
GPT 6.1 Review — ✅ no blocking findingsGPT 6.1 completed its review of This comment is updated in place on each push. Review detailsNo findings. False positive or not applicable? A repository writer can comment: |
Problem / Motivation
Goal:
docs/system-specs/modules/learn-cron-dashboard.mdmatches the code on current main.Several module specs name functions, owners and grant rows that moved or changed in code merged after the spec's last edit, and their prose still carries closed-issue and merged-PR numbers that
docs/system-specs/README.md("Writing a spec") forbids.Why it matters
A spec that names a function that does not exist, or leaves out a grant row the gate applies, sends the next reader (human or agent) to the wrong code and hides a real permission path.
Not a goal
modules/(sweep list B) andmodules/README.md..github/docs-lint-baseline.txtpruning: a separate finisher PR does those.What changed (motivation → approach → change)
Split out of #39898 because this one file's diff (about 1.5 MB) is over the Design Review 1 MB cap on its own: its paragraphs are single lines of up to ~180 KB, so any edit re-sends the whole line.
Approach: the file was read line by line against
origin/mainin 11 slices; each slice listed its concrete claims (names, paths, routes, config keys and defaults, events, numbers, behaviour), checked them in the source, and recorded a fix for each wrong, removed or missing item and each changelog-style sentence. Closed-issue and merged-PR numbers were removed from prose.257 fixes across the cron store and runs, the dashboard routes (skills, prompts, MCP, memory stores, project tree, capability routes), the chat and sidebar sections, the terminal and app-backend sections, and the monitor and loop sections. Examples: the shadow counting site is
shadow.py::run_shadow_probe; the mid-turn model pick answers200 {..., deferred: true}; review submission carriescontentDigest; the/api/capability/*routes are described in present tense; the product name is spelled Kiro Crew in prose.Backwards compatibility
Removes nothing: no code, key, route or file is removed; only doc sentences change.
Tests
Proof: not provable -- docs or config only
./scripts/docs-lint.shexits 0.Manual verification
N/A -- docs only; each changed claim was checked against the named symbol on main.
Real-machine verification
N/A -- docs only, the diff runs nothing.
Related Issues
Split from #39898.
Checklist
feat|fix|docs|style|refactor|perf|test|chore|ci|build|revert: ...); PR Hygiene does not count commitsContribution License Agreement
Contributions are accepted under the project's Apache-2.0 license.