Development record
itd-74 ac-5 promises the public family present after ahoy scaffolding; where the docs-lint config path is gitignored (TestPublicFamilyUnderPublicVisibility) install writes no public family and reports the gap as unresolvable, leaving that repo with no CI-enforced banned-names family
issueopenminoriss-2609261457353277
itd-74 ac-5 promises the public family present after ahoy scaffolding; where the docs-lint config path is gitignored (TestPublicFamilyUnderPublicVisibility) install writes no public family and reports the gap as unresolvable, leaving that repo with no CI-enforced banned-names family
Remedy grounds (2026-09-29)
- Why: the three answers D3 item 3 lists, each with its change; the ruling is unanswered and none is picked. The fence is the same one iss-2609100506269348 reports, so one planning interview should settle both.
- Rejected: taking the private layer as the whole answer without amending ac-5, which would leave a shipped promise false.
Frontmatter
| id | iss-2609261457353277 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2609261457353277-itd-74-ac-5-promises-the-public-family.md
open on GitHub ↗ · commit history ↗
mentions2
- iss-2609100506269348On a fresh PUBLIC repo the committed banned-names layer cannot be created, and the window in which it cannot is exactly the window in which a repo is being set up to ban a name.
- itd-74abcd Keeps the Names You Ban Out of Everything You Publish