cad-suggest: the tuner has no front door #110
Labels
No labels
already-shipped
bug
documentation
duplicate
enhancement
external-review
good first issue
help wanted
in progress
invalid
needs-decision
proposal
question
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: crenshawdev/cadence-archived#110
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
planning.mjs trace suggestalready reads the run record and returns ranked routing recommendations with the evidence behind each one. Nothing surfaces it.workflows/report.mdprints a one-line pointer at the end of/cad-report, and that is the entire discovery path: a user who does not run/cad-report, or who stops reading before its last line, never learns the tuner exists.Smallest honest version:
/cad-suggest, a skill atskills/cad-suggest/SKILL.mdthat relays the seam and presents each recommendation with the trace figures it rests on. It writes no config of its own - anything accepted goes through/cad-config, named by key, so the write face stays in one place. A trace too thin to clear the evidence floors reports that refusal in one line instead of inventing a suggestion to fill the space.Registration is part of the requirement, not a follow-up:
skills/cad-help,README.mdand.planning/DOCS-CLAIMS.md.Ordering: TRC-01 (#108) lands first. The coordinator events change what the evidence floors are computed over, so the command cannot correctly ship until those are in.