[bug] No setup step asks for the values in the CONFIG templates
I maintainer di solito rispondono entro 5 giorni
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 30/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- json, markdown, typescript
- Ambito
- devtools
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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) runsScaffoldUser.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.mdmentions 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:
- Setup and Update both end by running
SetupInventory.ts statusand walking the user through each system that needs setup or still holds template values, one question at a time, from that system's guide. - Update names the template files it just scaffolded and the system each one belongs to.
- 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.
- Lingua principale
- TypeScript
- Stelle
- 19.9k
- Fork
- 2.5k
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di danielmiessler/LifeOS
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 67/100
danielmiessler/LifeOS#2894 ·
I maintainer di solito rispondono entro 5 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
danielmiessler/LifeOS#2891 ·
I maintainer di solito rispondono entro 5 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
danielmiessler/LifeOS#2888 ·
I maintainer di solito rispondono entro 5 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
danielmiessler/LifeOS#2886 ·
I maintainer di solito rispondono entro 5 giorni
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 68/100
danielmiessler/LifeOS#2848 ·
I maintainer di solito rispondono entro 5 giorni
Tutte le issue di danielmiessler/LifeOS
Issue simili
-
ready-for-agent
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 86/100
LucasSantana-Dev/Lucky#3257 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
XiaomiMiMo/MiMo-Code#2849 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
enhancement frontend good first issue help wanted testing-infrastructure
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
I maintainer di solito rispondono entro 2 giorni
-
enhancement follow-up
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
obsidian-tasks-group/obsidian-tasks#4155 ·
I maintainer di solito rispondono entro 1 giorno