Outro names a report file the agent was told not to write
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 3/5
- 見積もり時間
- 1〜2日
- 初心者へのやさしさ
- 65/100
- issue の種類
- バグ
- 明瞭さ
- 明確に書かれている
- 活発さ
- 活発
- 技術スタック
- typescript
- 領域
- cli, documentation
調査の方向性
Start by reading the conflicting instructions in src/agent/tools/handoff.ts and src/agent/agent-prompt.ts. Then examine the outro logic in src/agent/runner/sequence/linear.ts and src/ui/tui/screens/OutroScreen.tsx to see where the report file name is used. The fix involves aligning the instructions and conditionally displaying the file path only if the file exists. Run a test program to verify the behavior.
索引モデルが issue の本文から書いたものです。
説明
Problem
Main now has part of the "report goes through publish_handoff" change, and the outros point at files that do not exist.
#1141 (merged 2026-08-27) added this clause to the publish_handoff description: "do not write the report to a file yourself". It is at src/agent/tools/handoff.ts:30-33 on main (d8486dc1), and the pi tool uses the same text. The rest of the code still asks for the file or says it exists:
skillPromptstill says "write a brief markdown report to ./${reportFile}" (src/agent/agent-prompt.ts:54). Every program with askillIdgets this line.- The context-mill skills still say to write it.
context/skills/data-warehouse-source/description.md:99says "write the report file requested by the wizard".context/skills/audit/references/6-report.md:7and:52say toWriteposthog-audit-report.mdto disk. context-mill#306 moves these skills topublish_handoff. It is still a draft. - The outros show the file name and never check the file exists.
src/agent/runner/sequence/linear.ts:294-300passesrun.reportFilethrough.src/ui/tui/screens/OutroScreen.tsx:87-93prints "Check ./… for details", andsrc/ui/tui/exit-line.ts:91-92adds the same line on exit.src/ui/tui/screens/audit/AuditOutroScreen.tsx:64-76prints "Report saved to:". The audit success message atsrc/lib/programs/audit/index.ts:48, the ledger row label atsrc/lib/programs/audit/seed.ts:99-103and the "Write report" slide atsrc/ui/tui/screens/audit/slides/writeReport.tsx:25also name the file. - On main,
publish_handoffwrites a file only when the host setsPOSTHOG_HANDOFF_OUTPUT_PATH. The TUI does not set it, so nothing is written to the project. - The wizard-workbench warehouse grader also expects the file. Its "report written" check passes only when
result.reportFile.existsis true (PostHog/wizard-workbenchservices/wizard-ci/warehouse-checks.ts:813-820), so a run that follows the tool description fails it.
Evidence
Each run follows one instruction or the other. We saw this in a real-TUI sweep of all nine programs on the refactor stack head d938a43b (#1307), which has the same code for this path as main:
- warehouse (
revenue/stripe/stripe-saas-demo): the agent called onlypublish_handoffand marked "Write setup report" completed. The outro says "Check ./posthog-warehouse-report.md for details". No file was written. - audit (
audit/posthog-demo-3000): the agent resolvedwrite-reportas pass: "Final markdown report delivered through the wizard handoff." The outro says "Report saved to: /posthog-audit-report.md". No file was written. The Release A top (200961f8) did the same. - metrics (
express-todo, orchestrator flow): the report went only to a notebook. The orchestrator outro does not name a file, so it shows nothing false. - ai-observability wrote its file and also called
publish_handoff. On 200961f8, warehouse wrote its file too. The result depends on which instruction the model follows.
The stack carries the same lines at other positions (src/agent/agent-prompt.ts:54, src/agent/tools/handoff.ts:33, src/agent/runner/sequence/linear.ts:314, src/ui/tui/screens/OutroScreen.tsx:107, src/ui/tui/screens/audit/AuditOutroScreen.tsx:67, src/programs/resolve-run-definition.ts:56), so this is not a stack regression.
Prior work
#1047 (open draft, last updated 2026-07-31, conflicting) makes publish_handoff the only report channel. It changes skillPrompt, stops programs naming a .md file, and shows the file in the outro only when one was written. context-mill#306 is its skill-side pair. Both are stale, and #1047 predates #1141, so it does not describe the contradiction main has now. Its base is ce8b70d3, and the files have moved since: src/lib/agent is now src/agent, and src/lib/wizard-tools is now src/agent/tools.
#811 (open draft, stale since 2026-07-06) gates the linear-runner outro on the file existing. It is on old paths and does not cover the audit success message or screen.
Suggested fix
- Now: pick one instruction. Either drop "do not write the report to a file yourself" from
PUBLISH_HANDOFF_DESCRIPTIONuntil the rest moves, or changeskillPromptto order apublish_handoffcall and stop naming the file. - Until one channel remains, show a report path only when that file exists in
installDir. #811 did this for the linear runner. The same check needs to cover the audit outro screen, the audit success message and the exit line. - Longer term: land #1047 and context-mill#306 together, or close them and do the same change on the current paths. Update the workbench "report written" check to accept the published handoff when the program no longer names a file.
- 主要言語
- TypeScript
- スター
- 204
- フォーク
- 54
- 平均マージ
- 1日 5時間
- マージ済み PR(30日)
- 51
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドなし
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
PostHog/wizard のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 66/100
PostHog/wizard#1460 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100
メンテナーはふだん 1 日以内に返信
-
Self-driving setup: checkbox labels and Confirm button overlap wrapped description text再び着手できるかも このイシューのプルリクエストはマージされずにクローズされました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
PostHog/wizard#986 · コメント 4 件 ·
メンテナーはふだん 1 日以内に返信
-
Intro shows "(detected)" after a manual pick from the detection-failed picker対応中かも @ShobhanKarthish が 72 日前に担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
メンテナーはふだん 1 日以内に返信
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 75/100
メンテナーはふだん 2 日以内に返信
-
nip98: validateEvent skips the payload check for a string or bytes body再び着手できるかも このイシューのプルリクエストはマージされずにクローズされました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
nbd-wtf/nostr-tools#599 ·
メンテナーはふだん 1 日以内に返信
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
LemmyNet/lemmy-ui#4442 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
Zettlr/Zettlr#6664 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
Microsoft Outlook add attachment reads the binary field from item 0対応中かも @joshbarros が今日担当しました。 オープンstatus:in-linear
難易度 2/5 1〜3時間 初心者へのやさしさ 85/100
メンテナーはふだん 1 日以内に返信