Skip to content

/ndd reports omit the PR url, so the reader has to reconstruct the link #304

Description

@thedavidmeister

Problem

/human-fsm:ndd reports omit the PR's url, so the human has to reconstruct a link from the owner/repo#n ref to open the thing they are ruling on.

Observed across four consecutive runs today. The row from next_design carries url and the command says to print every field of the row; the report printed the pr ref and dropped the url. It was present on the first two runs of the session and absent from the rest as the reports got longer — so the failure mode is drift under length, not a misread of the instruction.

Why the instruction alone does not fix it

"Print every field of the row" is already in the command, in two places, and it did not hold. A rule that depends on the writer re-reading a list of fields against their own prose is the class of thing that degrades exactly when the output gets long — which is when a reader most wants the link.

Ask

Make the URL structural rather than remembered.

  • State it as its own requirement, not as an instance of "print every field": the report opens with the PR's url verbatim from the row, on its own line or in the header table, before any analysis.
  • Same for the sibling read commands that present a subject — /nr, /ncc, /nm — so the shape is uniform and a reader learns one place to look.
  • Consider whether the shipped-command test in pr-review-report-rs/src/main.rs can assert it. It already parses command frontmatter and pins /nr's tool grant; a check that a presentation command's body requires the row's url would make this enforceable rather than aspirational, which is the difference between a rule and a wish here.

Not asked

Changing what the tools return. next_design, next_ready, next_close_candidate and next_leak all already carry url on the row. This is a presentation defect, not a data one.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions