Skip to content

docs(triage): refresh upstream issue and PR snapshots - #501

Merged
possiblyneal merged 2 commits into
mainfrom
possiblyneal/continue-previous-work
Nov 21, 2026
Merged

possiblyneal merged 2 commits into
mainfrom
possiblyneal/continue-previous-work

Conversation

@possiblyneal

@possiblyneal possiblyneal commented Nov 21, 2026 •

Copy link
Copy Markdown
Owner

Intent

Refresh the November 18 upstream triage snapshot and reconcile checked verdicts with fixes landed in this fork. The snapshot is a survey, not a backlog or a source of patches.

Read first

  • docs/upstream-issue-triage.yaml:35 — issue coverage and cross-link count.
  • docs/upstream-pr-triage.yaml:3 — orphan PR coverage and the input discrepancy.
  • Mechanical: added upstream records and their triage fields.

Decisions

  • Report 265 distinct cross-linked PRs and 305 orphan PR rows. The recorded input count was 573; the files do not identify the remaining three.
  • Keep partial fixes separate from unresolved claims. PR fix(facets): remove tags when their targets are deleted #500, for example, prevents new Facet orphans on ordinary deletion without sweeping existing orphans.

Out of scope

  • Runtime changes, upstream patches, and implementation decisions on remaining tickets.

Verified

  • Parsed both YAML files; verified unique row IDs, canonical URLs, allowed dispositions and status prefixes, required evidence, and disjoint cross-linked and orphan PR IDs.
  • git diff --check; the full local gate passed on 7f8fe051: clean install, build, generated hooks, skills, typecheck, Vitest (3,311 passed, one skipped), and both Recall gates.
  • Standard review: independent Standards+Spec and Correctness/Logic reviews; corrected findings are included in the gated head.

Not verified

  • The identities of the three PRs absent from the reported input count. Unchecked upstream claims are not reproduced by this PR.

Merge danger

Door: Two-way; reverting restores the previous snapshot.

Blast radius: The two upstream triage YAML files and readers of those snapshots. No runtime changes.

Refresh the dated upstream survey and reconcile checked verdicts with
fixes already landed in the fork. Record the PR coverage discrepancy
rather than treating the cached snapshot as a complete inventory.

Generated-By: gpt-6.2-sol
Distinguish fixes landed in this fork from unresolved portions of
upstream reports so the snapshot points readers at real gaps.

Generated-By: gpt-6.2-sol
@possiblyneal

Copy link
Copy Markdown
Owner Author

Code review: standard scan, clean.

Axes: Standards+Spec, Correctness/Logic

Reviewed-Head: 7f8fe05

@possiblyneal
possiblyneal merged commit cd5b0dd into main Nov 21, 2026
@possiblyneal
possiblyneal deleted the possiblyneal/continue-previous-work branch November 21, 2026 22:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant