ce-compound: refresh marks unsure learnings as stale, but no learnings researcher checks the mark

オープン
#2,090 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
49/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
typescript

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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-DD to 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_cause and severity from each candidate's frontmatter, then ranks on those fields (ce-plan/references/agents/learnings-researcher.md:129-160).
    It never reads status.
  • The copies under ce-code-review, ce-ideate and ce-optimize do the same.
    status: stale and stale_reason appear nowhere in skills/ 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):

  1. Have the learnings researchers read status and either skip stale docs or pass them on labeled as stale, with the stale_reason.
    Add status, stale_reason and stale_date, and title and category, to schema.yaml so tools that load it know about them.
  2. 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.

主要言語
TypeScript
スター
25.6k
フォーク
2.1k
平均マージ
3時間 55分
マージ済み PR(30日)
170

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

EveryInc/compound-engineering-plugin のほかの issue

EveryInc/compound-engineering-plugin の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。