Development record
2026-10-03 — The visibility question's public answer carries its caveat about records git already tracks only where `.abcd/` holds tracked files, and the flag hint every flagged question shares is reworded so its change-later line fits one row (the orchestrator of autonomous run A, 2026-10-03, choosing option (b) of iss-2610031236155833's "Fit 2026-10-03" choices because it drops no fact; applied by lane setupFit2). Core decides the per-repository help (`ahoy.HelpIn`, on the same evidence the install narrows the public ignore block on); the front door only renders it. Private's advice, that it suits a repository whose code is not published, stays.
2026-10-03 — The visibility question's public answer carries its caveat about records git already tracks only where .abcd/ holds tracked files, and the flag hint every flagged question shares is reworded so its change-later line fits one row (the orchestrator of autonomous run A, 2026-10-03, choosing option (b) of iss-2610031236155833's "Fit 2026-10-03" choices because it drops no fact; applied by lane setupFit2). Core decides the per-repository help (ahoy.HelpIn, on the same evidence the install narrows the public ignore block on); the front door only renders it. Private's advice, that it suits a repository whose code is not published, stays.
Frontmatter
| id | dcn-2610030000000005 |
|---|---|
| type | decision |
| date | 2026-10-03 |
.abcd/work/decisions/dcn-2610030000000005-the-visibility-question-s-public-answer.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2610031236155833abcd's own setup questions break the asking limits its question check enforces. docs_target offers four answers and oracle_backend five, so with the decide-later answer they exceed the four options per question that the check and the host's question tool allow; and under the provisional row estimate artefact_kind (33 rows), docs_target (28), oracle_backend (43), scan_deep (25), visibility (30) and the machine routing offer (42) exceed 24 rows at 80 columns. TestEverySetupQuestionPassesTheLimits holds them as a baseline that may only shrink.