Skip to content

Which upstream feature requests earn a test? #470

Closed

Description

@possiblyneal

Part of #448

Question

About 55 candidate rows are feature requests, not defects (tmp/upstream-review/ lists them: issues 259, 345, 392, 420, 433, 523, 524, 586, 595, 605, 620, 695, 730, 732, 765–770, 850, 880, 884, 899, 907, 919, 948, 981, 985, 1007, 1009, 1018, 1274, 1316, 1370, 1390, 1434, 1564, 1566; PRs 1247, 223, 467, 1011, 194, 241, 267, 376, 583, 617, 672, 679, 1779). Which address a cost the Operator actually pays, judged against the Goal and their Session history? Those get a verification ticket; the rest are rejected with the reason.

Activity

  1. self-assigned this
    on Nov 18, 2026
  2. possiblyneal commented on Nov 18, 2026

    @possiblyneal
    OwnerAuthor

    Resolution

    52 distinct items triaged (39 issues, 13 PRs); full table with evidence per item in tmp/verify/470/triage.md (local, quotes no transcripts).

    Retry if: the Operator starts using a record kind listed above as empty, or a missed-injection or replay measurement points at one of these features.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions