Skip to content

Commit a99ae2b

Browse files
authored
Record the upstream-report practice, and park the reference-report idea (#212)
Adds a practice: report an upstream gap we identify, not only the workaround around it. A dependency or tool we rely on is worth improving - report it with a reproduction and the evidence, keep the reference where the constraint bites with its close-out clause, and post it through the review gate like any outward-facing artifact. The workaround is ours to keep; the fix belongs where the defect is. Parks the upstream-reference report in docs/ideas.md, corrected against the tracker: two of the four references have already closed unnoticed - ben-manes/gradle-versions-plugin#755 (PR #1060) and spring-projects/spring-data-elasticsearch#3334 (PR #3337, filed by the repo owner) - while their constraint notes still read as open, which is the idea's thesis firing before the report exists. Two remain open: gradle-helm-plugin#145 (with a close-out) and anomalyco/opencode#48100 (without).
1 parent 28dee58 commit a99ae2b

2 files changed

Lines changed: 20 additions & 0 deletions

File tree

‎AGENTS.md‎

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -81,6 +81,13 @@ fix the findings before publishing. A false claim written into the repository is
8181
post to a public tracker is not. A comment drafted for `anomalyco/opencode#48100` was reviewed this way, and the review
8282
caught a wrong premise about permission-pattern expansion before it went public.
8383

84+
**Report an upstream gap we identify, not only the workaround around it.** A dependency or tool we rely on is worth
85+
improving: when a gap is identified — a spurious update row, a deprecation with no fix, a limitation that forces a
86+
workaround — report it upstream with a reproduction and the evidence, and keep the reference where the constraint bites,
87+
with the close-out clause for when it lands. The workaround is ours to keep; the fix belongs where the defect is, and an
88+
upstream project improves only if its users say what is wrong. Post it through the review gate like any outward-facing
89+
artifact.
90+
8491
**Interrogate the premise before designing a change that moves, copies, or removes existing configuration.** Establish
8592
_why the current state exists_ and whether it is deliberate before designing _how_ to change it — a change that
8693
relocates configuration already in place can be the best-executed version of the wrong idea. The

‎docs/ideas.md‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -43,6 +43,19 @@ section for a new day rather than appending to the most recent one).
4343
`showcaseCache`, which is how the drift passes it); the sibling `sagaCache`/`sagaAssociationsCache` and the gateway's
4444
query caches are aligned. Reconcile all the surfaces (Java, yml, chart, test) to one value in its own change.
4545

46+
- An upstream-reference report — parked; no change yet. Several durable-artifact notes point at upstream issues we are
47+
waiting on, and the first closures have already gone unnoticed: `ben-manes/gradle-versions-plugin#755` closed
48+
2026-08-06 (PR #1060) and `spring-projects/spring-data-elasticsearch#3334` closed 2026-08-30 (PR #3337), yet the
49+
constraint notes — the versions-plugin row and ADR-0007, and the `NANOS_DATE_PATTERN` gotcha — still read as open, and
50+
no gate reads them. Two others remain open: `build-extensions-oss/gradle-helm-plugin#145`, which carries an inline
51+
close-out, and `anomalyco/opencode#48100`, which has none (`#3334` has none either). The repository already has the
52+
shape for a watcher: `dependencyUpdates` / `helmUpdates` / `buildpackUpdates` are each a small task plus a weekly
53+
observational workflow that opens or updates an issue and mentions the owner when something is actionable. A report
54+
would collect the references from `AGENTS.md`, `README.md`, and `docs/adr/` — the corpus is all `owner/repo#NNN` plus
55+
one non-GitHub id (`KAFKA-18281`) — resolve them through the relevant API, and report the ones that closed or went
56+
quiet, turning the references into a checked corpus rather than claims. Worth building now: the trigger it describes
57+
has already fired twice.
58+
4659
## 2026-09-13
4760

4861
- Query-api → command-api re-export (dependency hygiene) — parked; no change yet. Found by the first

0 commit comments

Comments
 (0)