ce-compound: refresh marks unsure learnings as stale, but no learnings researcher checks the mark
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 49/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- developer-experience, documentation
Research direction
Start with the learnings researcher files under ce-plan, ce-code-review, ce-ideate, and ce-optimize, then compare how they read frontmatter with the stale marking rules in ce-compound's refresh references. Check schema.yaml against the resolution template as well. Decide how stale learnings should be handled, update the readers and schema or clarify the intended behavior, and ensure the report accurately describes whether marked learnings still inform later runs.
Written by the indexing model from the issue text.
Description
When ce-compound's refresh can't decide what to do with a learning, it marks the learning stale instead of acting.
Nothing that reads learnings checks that mark, so a stale-marked doc keeps grounding new plans and reviews as if it were current.
What refresh writes (skills/ce-compound/references/refresh/modes.md:10):
When classification is genuinely ambiguous or Replace evidence is insufficient, mark the doc stale instead: add
status: stale,stale_reason: [what you found],stale_date: YYYY-MM-DDto its frontmatter. Err toward stale-marking over incorrect action.
The interactive path does the same when evidence is insufficient (refresh/per-action-flows.md:128-133), and the report counts the result as "Marked stale" (refresh/report.md:16).
What the readers do:
- The learnings researcher that ce-plan dispatches reads
module,problem_type,component,tags,applies_when,symptoms,root_causeandseverityfrom each candidate's frontmatter, then ranks on those fields (ce-plan/references/agents/learnings-researcher.md:129-160).
It never readsstatus. - The copies under ce-code-review, ce-ideate and ce-optimize do the same.
status: staleandstale_reasonappear nowhere inskills/outside the refresh files above.
The schema doesn't define the mark either.
schema.yaml calls itself "the canonical frontmatter contract for compounded learnings" and carries a schema_version for tools that load it at a pinned ref (schema.yaml:1-13).
Its required and optional fields (schema.yaml:42-103, schema.yaml:189-221) don't include status, stale_reason or stale_date.
They also leave out the title and category lines the resolution template asks for (assets/resolution-template.md:14-17).
The cost: refresh's safe fallback for "I'm not sure this is still true" changes nothing for the next run.
A user who runs refresh unattended and sees "Marked stale: 3" in the report will still get those three docs quoted as constraints in the next plan.
Possible fixes (your call which matches the intent):
- Have the learnings researchers read
statusand either skip stale docs or pass them on labeled as stale, with thestale_reason.
Addstatus,stale_reasonandstale_date, andtitleandcategory, toschema.yamlso tools that load it know about them. - If stale docs are meant to keep grounding until a person looks at them, say so in
refresh/modes.md, and have the refresh report say that marked docs are still in use.
Found by reading the files at 8f76146, not by a live refresh run.
- Dominant language
- TypeScript
- Stars
- 25.6k
- Forks
- 2.1k
- Avg merge
- 3h 55m
- Merged PRs (30d)
- 170
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from EveryInc/compound-engineering-plugin
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
EveryInc/compound-engineering-plugin#2091 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
EveryInc/compound-engineering-plugin#795 · 1 comment ·
Maintainers usually reply within 1 day
-
Host support: DeepSeek Harness (dsh)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 3/5 1-2 days Newbie friendliness 48/100
EveryInc/compound-engineering-plugin#2072 ·
Maintainers usually reply within 1 day
-
Respect a user policy of working on the default branch (ce-commit, ce-debug, ce-worktree, ce-test-browser, ce-dogfood)Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 5/5 Over a week Newbie friendliness 22/100
EveryInc/compound-engineering-plugin#2071 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
EveryInc/compound-engineering-plugin#1832 · 1 comment ·
Maintainers usually reply within 1 day
All issues in EveryInc/compound-engineering-plugin
Similar issues
-
P2
Difficulty 1/5 Under an hour Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
bug ready-for-human
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
LucasSantana-Dev/Lucky#3150 ·
Maintainers usually reply within 1 day
-
enhancement good first issue priority: low size: XS
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
area: testing bug priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
snapotter-hq/SnapOtter#5099 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day