This is the record of an abcd-managed repository

abcdBetav0.16.2 · 2026-11-06

Development record

2026-10-04 — Decided without a question under the person's ruling that an obvious answer is decided (lane e8term3fix of autonomous run A, on sec-e8term3 finding 5; iss-2610040025088395): the gap with B3's "writes nothing" is split. This branch settles before the install's first write what is fixed before the run: every answers-file entry whose question has a fixed set of answers is checked against that set, and every config value the run would ask is walked by `ahoy.WalkConfigValueQuestions`, which follows the install's own collection (`collectMissingValues`), so those refusals write nothing and say so. The questions whose asking the run itself decides (the status line's elements, the routing and status-line offers, the lineage question, the house-style question, the artefact kind) are still checked when they are put, and their stop now says that what the steps before it changed stays; iss-2610040025088395 stays open for them, waiting on a question plan in core ahoy, the setup questions' owner's area. Why: the config values depend only on detection, the flags and two answers given before any write, so they can be settled without the plan, while the rest depend on state the steps before them write. Alternative not taken: holding the whole fix for the plan, which would leave the common case (a missing visibility leaving `.abcd/config.json` behind) open.

decisiondcn-2610040000000005

2026-10-04 — Decided without a question under the person's ruling that an obvious answer is decided (lane e8term3fix of autonomous run A, on sec-e8term3 finding 5; iss-2610040025088395): the gap with B3's "writes nothing" is split. This branch settles before the install's first write what is fixed before the run: every answers-file entry whose question has a fixed set of answers is checked against that set, and every config value the run would ask is walked by ahoy.WalkConfigValueQuestions, which follows the install's own collection (collectMissingValues), so those refusals write nothing and say so. The questions whose asking the run itself decides (the status line's elements, the routing and status-line offers, the lineage question, the house-style question, the artefact kind) are still checked when they are put, and their stop now says that what the steps before it changed stays; iss-2610040025088395 stays open for them, waiting on a question plan in core ahoy, the setup questions' owner's area. Why: the config values depend only on detection, the flags and two answers given before any write, so they can be settled without the plan, while the rest depend on state the steps before them write. Alternative not taken: holding the whole fix for the plan, which would leave the common case (a missing visibility leaving .abcd/config.json behind) open.

Frontmatter

iddcn-2610040000000005
typedecision
date2026-10-04

mentions1