issue-create ends the Origin section at an inline heading mark and refuses a valid body #965
Labels
No labels
P0
P1
P2
P3
bug
category/code-change
category/cross-repo
category/eval-run
category/investigation
category/no-test-target
category/owner-ruling
category/prose-artifact
category/recurring-chore
category/structure
category/umbrella
crc-refactor
create
delete
enhancement
filed-by/agent
filed-by/user
frozen
lint-rule
needs-info
needs-triage
next
plugin/cc-architect
plugin/os
plugin/os-adr
plugin/os-aidd-lint
plugin/os-backlog
plugin/os-context
plugin/os-doc-hygiene
plugin/os-sdlc
plugin/os-vault
project/cc-os
ready-for-agent
ready-for-human
recurring
review
rule-proposal
update
waiting
wayfinder:grilling
wayfinder:map
wayfinder:map
wayfinder:research
wayfinder:task
wayfinder:task
wontfix
worklist/deviations
worklist/lint-rule
worklist/new-implement-build
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
jared/cc-os#965
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Problem
issue-createends the Origin section at the first##text, even in the middle of a line. A valid body that names a heading inside the Origin block is refused. The error names the wrong cause: it says the required lines are missing, but they are present.Observed
plugins/os-backlog/lib/backlog/issue_create.rb:78:A body whose Origin block had the line
- Chain: ... makes \## Approach` "optional at capture"` and then Session:, Transcript: and Where: lines was refused:The same body was accepted after that one line was reworded (it became #960).
Reproduce
Acceptance criteria
##in the middle of a line, whenissue-createchecks it, then it finds the Session:, Transcript: and Where: lines that follow.issue-createchecks it, then the Origin section ends at that heading line.Origin
/os-backlog:captureof #960 in this sessionDESIGN: the end pattern is not anchored to line start (issue_create.rb:78)VERDICT: CREATE — observed while filing #960; the error names the wrong cause; the end pattern is the root.
A second form of the same defect, seen while filing this ticket: the start pattern is not anchored either. The parser starts the Origin section at the first
## Origintext anywhere, including inside a code block in Observed or Reproduce. This body had to be filed short and then edited for that reason.Acceptance criterion to add: Given a body that quotes the Origin heading inside a code block before the real Origin heading, when issue-create checks it, then it reads the real Origin section.
Occurrence: issue-create Origin check ends the block at inline
##textSeen: plugins/os-backlog/lib/backlog/issue_create.rb:78 (pattern not anchored to line start)
Run: Session 22b441ac-a301-4637-8de9-a9e0f0970fae, filing #1153
Adds: a Trigger line naming HANDOFF.md
## Reviewinside a code span gave 'the ## Origin block is missing required line(s): Session:, Transcript:, Where:' with all three present; rewording the Trigger line cleared it.Occurrence: os-backlog issue-create cuts the Origin block at any '## ' inside a line
Seen: plugins/os-backlog/lib/backlog/issue_create.rb:89 (origin_section lookahead not line-anchored)
Run: Session 4f3f95ea-3c6f-4d23-a0ea-e349d6ab02a5, 2026-10-23, while filing #1289
Adds: a Chain line quoting a markdown heading (Prediction heading in backticks) caused a refusal for missing Session:, Transcript:, Where:; the author reworded the line to work around it.