Compare commits
1 Commits
| Author | SHA1 | Date | |
|---|---|---|---|
| cc38bcd700 |
+20
@@ -35,6 +35,26 @@ dev-checkout concern - readable here, never shipped as something to parse.
|
|||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
|
## 4.7.4 - 2026-09-04 - bootstrap.md nennt den session-id-WARN nach frischem Bootstrap explizit als erwartet
|
||||||
|
|
||||||
|
**Author:** Torben Nehmer
|
||||||
|
|
||||||
|
<!-- wikitool:bumps -->
|
||||||
|
- bootstrap.md nennt den session-id-WARN nach frischem Bootstrap explizit als erwartet
|
||||||
|
<!-- /wikitool:bumps -->
|
||||||
|
|
||||||
|
Nach einem frischen Clone plus `instructions/bootstrap.md` zeigte `tools/wikitool doctor`
|
||||||
|
durchgehend `OK`, außer `session-id: WARN` - ohne Einordnung, ob das ein Bootstrap-Defekt ist.
|
||||||
|
`WIKITOOL_SESSION_ID` wird laut `instructions/session-setup.md` bewusst pro Arbeitssitzung
|
||||||
|
gesetzt, nicht pro Clone; ein Export in `bootstrap.md` selbst würde nur für den Bootstrap-Lauf
|
||||||
|
gelten, nicht für die tatsächliche Arbeitssitzung danach (die nach dem Neustart in Schritt 6 in
|
||||||
|
einer neuen Shell beginnt). `bootstrap.md` bekommt deshalb einen neuen Schritt 7, der den WARN
|
||||||
|
als erwarteten Zustand benennt - analog zum bereits dokumentierten `personalization: FAIL` in
|
||||||
|
Schritt 4 - und auf `session-setup.md` verweist, statt den Export in Bootstrap nachzubauen.
|
||||||
|
Schließt #54.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
## 4.7.3 - 2026-09-04 - eval: gate-not-self-opened prueft REMOVED_FLAGS gegen das eigene Kommando
|
## 4.7.3 - 2026-09-04 - eval: gate-not-self-opened prueft REMOVED_FLAGS gegen das eigene Kommando
|
||||||
|
|
||||||
**Author:** Torben Nehmer
|
**Author:** Torben Nehmer
|
||||||
|
|||||||
@@ -65,6 +65,14 @@ they are published: the agent harness will not offer `wiki-ingest`, `wiki-query`
|
|||||||
6. **Restart the agent session** if it was already running. Harnesses read the skill
|
6. **Restart the agent session** if it was already running. Harnesses read the skill
|
||||||
directories at startup, so skills published mid-session are not picked up.
|
directories at startup, so skills published mid-session are not picked up.
|
||||||
|
|
||||||
|
7. **Expect a lingering `session-id` WARN.** A `tools/wikitool doctor` run at this point reports
|
||||||
|
`OK` throughout except `session-id: WARN` - that check is scoped to the working session, not
|
||||||
|
the clone, so a freshly bootstrapped checkout with no `WIKITOOL_SESSION_ID` exported yet
|
||||||
|
always shows it. This is expected, not a Bootstrap gap: exporting it here would only be true
|
||||||
|
for this one-off setup run, not for whichever session picks up the actual work next, in a new
|
||||||
|
shell after step 6's restart. Run [session-setup.md](session-setup.md) at the start of that
|
||||||
|
session instead.
|
||||||
|
|
||||||
## Scope
|
## Scope
|
||||||
|
|
||||||
This does not apply to anything under `kb/`, `raw/` or `reports/`; those are committed and
|
This does not apply to anything under `kb/`, `raw/` or `reports/`; those are committed and
|
||||||
|
|||||||
Reference in New Issue
Block a user