standards: per-concern standards layout - part 2 of 2 #10232

Activity

1. melodic-automation-lanes

   added the

   Task

   issue type on Oct 26, 2026
2. melodic-automation-lanes

   added a parent issue on Oct 26, 2026

   • standards: per-concern standards layout #7583
3. melodic-automation-lanes

   marked this as blocked on Oct 26, 2026

   • standards: per-concern standards layout - part 1 of 2 #10231
4. melodic-automation-lanes

   marked this as blocking 2 issues on Oct 26, 2026

   • review: spec-first fanout and ratchet move to toolchain #7584
   • architecture: boundaries and conventions lenses #7590
5. github-actions

   added

   needs-triageNot yet classified. Floor until a type and one priority tier are set.Not yet classified. Floor until a type and one priority tier are set.

   on Oct 26, 2026
6. github-actions commented on Oct 26, 2026

   

   github-actionsBot

   on Oct 26, 2026 – with GitHub Actions

   Last edited by melodic-automation-lanes

   Contributor

   More actions

   Proposed work class: work-class: scoped
   Basis: automated intake triage; the lanes App applied this class.

   Size: Medium
   Complexity: Medium
   Uncertainty: Knowable
   Flags: intent
   Blocked by: #10231

   I understand this is part 2 of 2 of #7583, split at intake. Its done-when has two items. The first, about the drift check exiting non-zero after a hand edit inside a generated block of a fixture copy, ends mid-sentence at "and". The second is that every slice sub-issue is closed by a merged PR. Part 1 is #10231.

   Open questions:

   1. What is the rest of the first done-when item, after "and"? RECOMMENDED: copy the full line from standards: per-concern standards layout #7583. Basis: the split copied it as written and the text was cut.
   2. Which slice sub-issues does the second item cover? RECOMMENDED: list them here by number. Basis: the item names no issues, so it can't be checked.
   3. Should this wait for standards: per-concern standards layout - part 1 of 2 #10231? RECOMMENDED: yes. Basis: judgment, since part 2 appears to depend on the layout work in part 1.

   _{Automated triage, applied by the lanes App.}
7. github-actions

   added

   priority: mediumReal value, no hard deadline; normal backlog flow.Real value, no hard deadline; normal backlog flow.

   status: needs-decisionAwaiting a human or maintainer judgment call.Awaiting a human or maintainer judgment call.

   on Oct 26, 2026
8. melodic-automation-lanes commented on Oct 26, 2026

   

   melodic-automation-lanesBot

   on Oct 26, 2026

   ContributorAuthor

   More actions

   The triage verdict left this issue at status: needs-decision:

   • flagged: intent
   • held by status: needs-decision
   • no lanes App verdict comment shows whether an earlier verdict was flagged
9. melodic-automation-lanes

   added

   work-class: scopedA briefed fix or small feature; blast radius bounded by the brief, tests exist.A briefed fix or small feature; blast radius bounded by the brief, tests exist.

   and removed

   needs-triageNot yet classified. Floor until a type and one priority tier are set.Not yet classified. Floor until a type and one priority tier are set.

   on Oct 26, 2026
10. melodic-automation-lanes commented on Oct 26, 2026

    

    melodic-automation-lanesBot

    on Oct 26, 2026

    ContributorAuthor

    More actions

    Refinement. A read-only run explored this repository, searched its issues and pull requests, and read the allowed docs to draft what follows. On an issue a listed human filed, it counts as the issue's spec once posted, while unedited; it is still model text, so check it.

    Intended outcome: A drift check fails on hand edits inside generated blocks of the per-concern standards layout, and all slice sub-issues of #​7583 are closed by merged PRs.

    Dependencies

    • #​10231: part 1 of 2 delivers the per-concern layout this part checks

    Related work

    • standards: per-concern standards layout - part 1 of 2 #10231 (related): Part 1 of 2 of the same split; this part depends on it.
    • standards: per-concern standards layout #7583 (related): Parent issue; holds the full done-when text and the slice sub-issues.

    Open questions

    1. What is the rest of the first done-when item after 'and'? It reads 'exits non-zero after a hand edit inside a generated block of a fixture copy and' and stops there.
       RECOMMENDED: Copy the full line from #​7583 into this issue. Basis: judgment
    2. Which slice sub-issues does 'every slice sub-issue is closed by a merged PR' cover?
       RECOMMENDED: List the sub-issue numbers in the body. An unattended run cannot check an unnamed set. Basis: judgment
    3. Should this wait for #​10231?
       RECOMMENDED: Yes. The drift check needs the layout and generated blocks from part 1. Basis: 10231
    4. Is the second item something a person should verify rather than an unattended run, since it depends on other PRs merging?
       RECOMMENDED: Yes. Treat it as a person-run check, or drop it from this issue's done-when. Basis: judgment

    Sources read

    • /home/runner/work/_temp/refine-data/context.json: issue body done-when is truncated at 'and'; triage lists Blocked by #​10231

    _{Automated refinement by the lanes App. Answer with a comment whose first line is **Decision recorded.**.}