-
Notifications
You must be signed in to change notification settings - Fork 1
All issues
Issue creation is restricted in this repository
Issues
is:issue state:open
is:issue state:open
Search results
- Status: Open.#1783 In afokapu/atdd;
The repository has no documentation system: 89 markdown files carry no current-vs-historical boundary, nothing renders them, and no issue is ever required to say what it documented
atdd-issueATDD parent issueATDD parent issueatdd:INITATDD phase: INITATDD phase: INITStatus: Open.#1782 In afokapu/atdd;The work_item carries no phase, so every lifecycle decision depends on the GitHub label and no git hook can enforce the phase machine
atdd-issueATDD parent issueATDD parent issueatdd:INITATDD phase: INITATDD phase: INITStatus: Open.#1781 In afokapu/atdd;The function-length ratchet counts docstring lines as code, so documenting a function is indistinguishable from making it complex: 15 of the 66 baselined violations are under the limit once prose is excluded
atdd-issueATDD parent issueATDD parent issueatdd:INITATDD phase: INITATDD phase: INITStatus: Open.#1777 In afokapu/atdd;A merged PR closes every open sub-issue of the issue it links, whatever phase the child is in: eight unstarted issues closed in ten seconds, and the store was never told
atdd-issueATDD parent issueATDD parent issueatdd:INITATDD phase: INITATDD phase: INITStatus: Open.#1776 In afokapu/atdd;Retirement is unsafe: the succession guard has no production caller, the fail-closed route is unwired, and a substrate-less consumer gets 62 PASS verdicts
atdd-issueATDD parent issueATDD parent issueatdd:INITATDD phase: INITATDD phase: INITStatus: Open.#1775 In afokapu/atdd;Extension declarations cannot be authority: 15 nodes already carry no legacy_rule_id and nothing represents them, so the succession guard is blind to them
atdd-issueATDD parent issueATDD parent issueatdd:INITATDD phase: INITATDD phase: INITStatus: Open.#1774 In afokapu/atdd;Bound provider realizations cannot discharge reverse coherence, so every enforced rule keeps a ceremonial core validator
atdd-issueATDD parent issueATDD parent issueatdd:REDATDD phase: REDATDD phase: REDStatus: Open.#1773 In afokapu/atdd;Program: make bound realizations first-class enforcement proof and complete convention authority succession
atdd-issueATDD parent issueATDD parent issueatdd:INITATDD phase: INITATDD phase: INITStatus: Open.#1772 In afokapu/atdd;Schemas are not the source of truth for the rules they define: 10 of 49 are authoritative, and no bind_schema contract exists to require it
atdd-issueATDD parent issueATDD parent issueatdd:INITATDD phase: INITATDD phase: INITStatus: Open.#1771 In afokapu/atdd;The toolkit blocks pushes to tell a human to run an upgrade it could run itself at a safe, non-blocking trigger
atdd-issueATDD parent issueATDD parent issueatdd:INITATDD phase: INITATDD phase: INITStatus: Open.#1762 In afokapu/atdd;Projects v2 residue still bootstraps in atdd init and writes live GraphQL from post-merge-lifecycle
atdd-issueATDD parent issueATDD parent issueatdd:INITATDD phase: INITATDD phase: INITStatus: Open.#1761 In afokapu/atdd;