[bug] No setup step asks for the values in the CONFIG templates

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

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

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

評価

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

調査の方向性

Start with install/LIFEOS/TOOLS/SetupInventory.ts (its status mode) and ScaffoldUser.ts, then read the Setup step 7 in Intents/Setup.md and step 3c in Intents/Update.md. Done means Setup and Update both run SetupInventory.ts status and list the template files they leave unfilled. This is a flow design change, so agree the wording of the questions with the maintainers first.

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

説明

What happened

After setup or an update, most files in the CONFIG folder still hold their template values (quiet hours, the daily text budget, the overage ceiling, placeholder account emails), and no step of Setup, the Interview or Update asks the user to fill them in.

Summary

[!NOTE]
🤖 Avi (AI assistant) writing on behalf of Hans-Jakob. He read and approved this text before it was posted.

Several files in the user tree's CONFIG/ folder steer live behaviour, but they arrive as templates and nothing in the install or update flow asks the user to fill them in. They keep their template values until someone opens the folder by hand.

Examples, each read by running code on 8.761.0:

File What it controls Template value
heartbeat.json quiet hours for every text to the user (QuietHours.ts, read by Vigil and AgentJob) 23:30 to 07:00
notifications.json the daily text budget across every sender (Interruptions.ts), which Vigil uses once decider_mode is enforce 12
overage.json the monthly ceiling for the overage lane (Overage.ts) 0, so the built-in default applies
anthropic-accounts.json the logins LIFEOS/ROUTER/FableBudget.ts reads a placeholder email address
achilles.json the stack_terms that Achilles.ts uses example terms

Where each flow stops:

  • Setup (Intents/Setup.md, step 7) installs everything "with placeholders where personal data goes until the Interview fills them in".
  • The Interview (Intents/Interview.md) fills identity, the DA's name and voice, and TELOS. It does not touch these files.
  • Update (Intents/Update.md, step 3c) runs ScaffoldUser.ts, which "adds template files new in this version" without telling the user that any of them need values.
  • Setup, Update and Doctor never run SetupInventory.ts status, the one tool that maps each file to its setup guide. GETTING-STARTED.md mentions it, but no intent calls it.

None of the five files above is written by any tool under LifeOS/Tools/. Setup step 5b already fills inference-vendor.json from the CLI logins, so the pattern of asking or detecting exists for one file.

#2633 covers the readiness check itself: template-hashes.json is missing from the release, so status reports every system as ready. Fixing #2633 makes the gap visible to anyone who runs status, but no flow runs it for the user.

Suggested change:

  1. Setup and Update both end by running SetupInventory.ts status and walking the user through each system that needs setup or still holds template values, one question at a time, from that system's guide.
  2. Update names the template files it just scaffolded and the system each one belongs to.
  3. Where a template value is a working default (quiet hours, the daily text budget), the setup guide says so, so a user who skips the question knows what they get.

Checked against upstream main (8.761.0): Intents/Setup.md, Intents/Update.md, Intents/Interview.md, GETTING-STARTED.md and install/LIFEOS/TOOLS/SetupInventory.ts are byte for byte the same as ours, and upstream's install/LIFEOS/TOOLS/Doctor.ts has no reference to SetupInventory.

Details

  • Kind: bug
  • LifeOS version: 8.761.0

Filed with the LifeOS /feedback command. The reporter approved this exact text before it was sent; paths, secrets and personal details were stripped locally.

主要言語
TypeScript
スター
19.9k
フォーク
2.5k
PR マージ指標
30日以内にマージされた PR はありません

環境構築

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

はじめの一歩

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

danielmiessler/LifeOS のほかの issue

danielmiessler/LifeOS の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

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

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