You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 9eb3a10
Browse filesBrowse the repository at this point in the historyBrowse files
## Closure policy for THIS run (user decision, 2026-08-18)
45
+
46
+
> "이슈는 dev 머지되면 일단 닫아놔 이번 런만 그런거야"
47
+
48
+
Close issues when the fix reaches `dev`, not when it reaches a stable release. **Scoped to this
49
+
run only** — the standing preference remains close-on-release, so a future campaign should not
50
+
read this as precedent.
51
+
52
+
What this changes: the `released-in:vX.Y.Z` step no longer gates closure. What it does *not*
53
+
change is the evidence bar — a close still needs the fix demonstrably on `origin/dev` by
54
+
ancestry, and still must not close an umbrella from a partial fix. The three policy holds keep
55
+
their own reasons, which are about missing evidence rather than about release timing:
56
+
57
+
| Issue | Still open because |
58
+
|-------|--------------------|
59
+
|#1059| needs hosted Windows shard evidence; no local batch substitutes |
60
+
|#1795| needs a live SenseNova/Kimi canary showing zero undeclared calls |
61
+
|#1852| the reported defect (sync enumeration blocking the event loop) is #1876's unmerged async work |
62
+
|#1849| umbrella; its root cause is #1942 and unstarted |
63
+
|#1049| assessed and unstarted; needs the publication protocol |
64
+
|#1926| destination scope landed, but credential scope and emit-before-commit are still live in `src/bridge.ts`|
65
+
|#1866| explicitly scoped out of #1900; no PR addresses it |
66
+
|#1730| different provider and round from #1884's ClinePass replay fix |
67
+
68
+
Two **pull requests** are also held, and they belong in this record even though the table
69
+
above is about issues — a reader working only from this document would otherwise see no trace
70
+
of them:
71
+
72
+
| PR | Held because |
73
+
|----|--------------|
74
+
|#1891| it makes `GOOGLE_ANTIGRAVITY_USER_AGENT` steerable into the `onboardUser` request body, violating this wave's accept criterion. Needs #1889 first, which is the one-line fix that makes `ide_version` a real constant. Detail in `080`. |
75
+
|#1889| unsponsored `src/oauth/` surface, plus still draft. The `maintainer-sponsored` label is the record that a security review happened, so an agent applying it would falsify that record. |
76
+
77
+
Neither is affected by the close-on-dev-merge decision: both are blocked *before* merge, so the
78
+
policy that governs when a merged fix closes its issue never reaches them.
0 commit comments