Record D-083 backlog disposition: re-home excluded wontfix requirements, correct #183/#186 prerequisites

kilo commented

2026-10-27 21:23:25 +00:00

Member

Goal

Record the owner's 2026-10-27 backlog disposition (next decision identifier D-083) in canonical repository documentation and Forgejo state, re-home still-required functionality from the six excluded historical wontfix issues to active owners, and correct the stale/inverted prerequisites of #183/#186 so /loop selection is no longer frozen by excluded issues. One coherent governance delivery; no product code changes.

Owner Authorization

Direct owner directive of 2026-10-27T21:19Z approving the 2026-10-27 read-only reconciliation recommendations. It authorizes: recording the decision, re-homing, native-dependency correction, minimal successor registration, P1 prioritization of the verified #165 cancellation defects, implementing/integrating independently eligible work through the established workflow, and returning to normal /loop continuation. It does not authorize production release, deployment, signing, live provider calls, weakening security guarantees or retiring working functionality. The 2026-10-05 wontfix labels keep their history; D-083 records a prospective correction, not a retrospective reason for the original labels.

Why and Evidence

The 2026-10-27 investigation (base 4a182affa4775a4a38b47860ad7622a099c56c4a) established: the six wontfix labels (applied 2026-10-05) have no recorded rationale; accepted requirements remained assigned to excluded issues (D-056 tier-B transport assigned to #139 in docs/security.md; admin-state correctness to #140 in docs/roadmap.md; composed acceptance to #141); #183/#186 declared prerequisites on excluded issues that can never run; and #165's four cancellation paths plus #166's fixture race remain present in current source. Full evidence: file:line citations in successor issues #224/#225/#226/#227.

Registered Successors (this delivery)

Excluded issue	Re-homed content	Active owner
#139	D-056 tier-B same-host container transport, CA trust persistence, certificate lifecycle, origin migration	#224 (security-critical)
#140	Producer-owned resource-state correctness (derived/discovered representation, honest availability/freshness, stable projection, no fabrication)	#183 (scope integration)
#140	Administrator-facing remainder (derived-resources display, honest counters, revoked-worker deletion, limits visibility, state-aware remediation)	#226
#141	Composed Tier-2/Tier-3 harness and installed acceptance (downstream stage)	#227
#165	Four cancellation/disconnect defects (P1)	#225
#166	None — recorded as an accepted test-infrastructure limitation (no new issue absent a concrete CI failure or demonstrated product impact)	— (D-083 record)
#132	None beyond the above — program framing superseded by D-056; children A–F delivered	—

Scope

docs/decisions.md: add D-083 (owner disposition; re-homing table with old issue, new owner, stage and retained invariant; prospective-correction framing).
docs/roadmap.md, docs/security.md, docs/release-engineering.md, docs/m10-acceptance.md, docs/control-surface.md, docs/architecture.md: point current-facing references from excluded #139/#140/#141/#165 to #224/#226/#227/#225 and #183 as appropriate. Historical decision text is not rewritten.
Forgejo native state (direct MCP, part of this delivery): #183/#186 body prerequisite corrections; remove native edges #183→#140, #186→#139, #186→#141; add #227→#183 and #227→#186 (composed acceptance follows components); read dependencies back in both directions and verify no cycles or inverted prerequisites; factual forward-pointer comments on #132/#139/#140/#141/#165/#166.
No changes to the six historical issues' labels, state or original text.

Acceptance Criteria

D-083 recorded with the full re-homing table and retained invariants; historical decisions untouched.
Every current-facing doc reference to the excluded issues' content resolves to an active owner; no reference presents an excluded issue as a blocking prerequisite.
Native dependency graph verified cycle-free in both directions; #183/#186 selectable without excluded predecessors; #227 ordered after its component producers.
Full gate (uv sync --only-dev, make check, uv run basedpyright, git diff --check) on the documentation-only diff; fresh independent review at exact frozen HEAD/base; merge under the 2026-10-27 authorization; this issue closed after verified integration.

Constraints

Documentation and Forgejo governance only; no product code, public contract, label/state change on historical issues, release/tag/deploy/signing/live-call authority. Forgejo references only (no GitHub mirror references).

Links

Owner directive 2026-10-27T21:19Z; reconciliation base 4a182af; successors #224, #225 (P1), #226, #227; corrected #183, #186; historical #132, #139, #140, #141, #165, #166; D-056, D-069, D-081; .kilo/command/loop.md.

## Goal Record the owner's 2026-10-27 backlog disposition (next decision identifier **D-083**) in canonical repository documentation and Forgejo state, re-home still-required functionality from the six excluded historical `wontfix` issues to active owners, and correct the stale/inverted prerequisites of #183/#186 so `/loop` selection is no longer frozen by excluded issues. One coherent governance delivery; no product code changes. ## Owner Authorization Direct owner directive of 2026-10-27T21:19Z approving the 2026-10-27 read-only reconciliation recommendations. It authorizes: recording the decision, re-homing, native-dependency correction, minimal successor registration, P1 prioritization of the verified #165 cancellation defects, implementing/integrating independently eligible work through the established workflow, and returning to normal `/loop` continuation. It does **not** authorize production release, deployment, signing, live provider calls, weakening security guarantees or retiring working functionality. The 2026-10-05 `wontfix` labels keep their history; D-083 records a **prospective** correction, not a retrospective reason for the original labels. ## Why and Evidence The 2026-10-27 investigation (base `4a182affa4775a4a38b47860ad7622a099c56c4a`) established: the six `wontfix` labels (applied 2026-10-05) have no recorded rationale; accepted requirements remained assigned to excluded issues (D-056 tier-B transport assigned to #139 in `docs/security.md`; admin-state correctness to #140 in `docs/roadmap.md`; composed acceptance to #141); #183/#186 declared prerequisites on excluded issues that can never run; and #165's four cancellation paths plus #166's fixture race remain present in current source. Full evidence: file:line citations in successor issues #224/#225/#226/#227. ## Registered Successors (this delivery) | Excluded issue | Re-homed content | Active owner | |---|---|---| | #139 | D-056 tier-B same-host container transport, CA trust persistence, certificate lifecycle, origin migration | **#224** (security-critical) | | #140 | Producer-owned resource-state correctness (derived/discovered representation, honest availability/freshness, stable projection, no fabrication) | **#183** (scope integration) | | #140 | Administrator-facing remainder (derived-resources display, honest counters, revoked-worker deletion, limits visibility, state-aware remediation) | **#226** | | #141 | Composed Tier-2/Tier-3 harness and installed acceptance (downstream stage) | **#227** | | #165 | Four cancellation/disconnect defects (P1) | **#225** | | #166 | None — recorded as an accepted test-infrastructure limitation (no new issue absent a concrete CI failure or demonstrated product impact) | — (D-083 record) | | #132 | None beyond the above — program framing superseded by D-056; children A–F delivered | — | ## Scope 1. `docs/decisions.md`: add D-083 (owner disposition; re-homing table with old issue, new owner, stage and retained invariant; prospective-correction framing). 2. `docs/roadmap.md`, `docs/security.md`, `docs/release-engineering.md`, `docs/m10-acceptance.md`, `docs/control-surface.md`, `docs/architecture.md`: point current-facing references from excluded #139/#140/#141/#165 to #224/#226/#227/#225 and #183 as appropriate. Historical decision text is not rewritten. 3. Forgejo native state (direct MCP, part of this delivery): #183/#186 body prerequisite corrections; remove native edges #183→#140, #186→#139, #186→#141; add #227→#183 and #227→#186 (composed acceptance follows components); read dependencies back in both directions and verify no cycles or inverted prerequisites; factual forward-pointer comments on #132/#139/#140/#141/#165/#166. 4. No changes to the six historical issues' labels, state or original text. ## Acceptance Criteria 1. D-083 recorded with the full re-homing table and retained invariants; historical decisions untouched. 2. Every current-facing doc reference to the excluded issues' content resolves to an active owner; no reference presents an excluded issue as a blocking prerequisite. 3. Native dependency graph verified cycle-free in both directions; #183/#186 selectable without excluded predecessors; #227 ordered after its component producers. 4. Full gate (`uv sync --only-dev`, `make check`, `uv run basedpyright`, `git diff --check`) on the documentation-only diff; fresh independent review at exact frozen HEAD/base; merge under the 2026-10-27 authorization; this issue closed after verified integration. ## Constraints Documentation and Forgejo governance only; no product code, public contract, label/state change on historical issues, release/tag/deploy/signing/live-call authority. Forgejo references only (no GitHub mirror references). ## Links Owner directive 2026-10-27T21:19Z; reconciliation base `4a182af`; successors #224, #225 (P1), #226, #227; corrected #183, #186; historical #132, #139, #140, #141, #165, #166; D-056, D-069, D-081; `.kilo/command/loop.md`.

kilo referenced this issue

2026-10-27 21:24:30 +00:00

Representative-client compatibility + operations hardening program (ZCode acceptance follow-up) #132

kilo referenced this issue

2026-10-27 21:24:31 +00:00

G. TLS + certificate lifecycle (public-CA direction, private-CA fallback) #139

kilo referenced this issue

2026-10-27 21:24:38 +00:00

H. Administrator UX cleanup (derived resources, honest counters, revoked-worker deletion, limits + client integration) #140

kilo referenced this issue

2026-10-27 21:24:40 +00:00

I. Integrated acceptance + coherent install/first-run + program closeout #141

kilo referenced this issue

2026-10-27 21:24:49 +00:00

Cancellation/disconnect semantics: close gaps outside the established-stream path #165

kilo referenced this issue

2026-10-27 21:24:50 +00:00

Flaky test fixture: fake-process _feed thread can write after pipe close #166

adrian.tkacz referenced this issue from a commit

2026-10-27 21:41:24 +00:00

Record D-083 backlog disposition and re-home excluded requirements (#228)

kilo referenced this issue

2026-10-27 21:41:30 +00:00

Record D-083 backlog disposition: re-home excluded wontfix requirements (#228) #229

kilo referenced this issue

2026-10-28 11:07:10 +00:00

Record D-083 backlog disposition: re-home excluded wontfix requirements (#228) #229

kilo referenced this issue from a commit

2026-10-28 11:25:47 +00:00

Merge pull request #229: D-083 backlog reconciliation

kilo commented

2026-10-28 11:26:10 +00:00

Author

Member

Completed/integrated via PR229 on 2026-10-28: merge2c40e0e1fb79397c97e6fa2b7dac0365d9712c0c on develop, parents approved base4a182affa4775a4a38b47860ad7622a099c56c4a and HEAD3fc37bb7ee8b6d259ad30b1f373013392e745e0c. Fresh Git verifies both ancestors and integrated tree exactly equals the approved HEAD. Independent GLM-5.3 native read-only review ordinal5/10, sessionses_e7dc3852cffeKCSo42D201Kbcr: APPROVE/findings[]/UX:none. Prior failed creation history1–4 retained. Validation3057 tests OK/16 skips,basedpyright0/0/0,whitespace clean. Acceptance verified: additive D-083 +8 current-facing docs; six historical issues remain open/wontfix; successors224/225(P1)/226/227;183/186 body corrections; bidirectional graph183->[179 closed],186->[185 closed],227->[183,186], no excluded predecessors/cycles. This closes governance only, not successor features/platform acceptance or release. Continuing existing225/PR230, then owner-authorized loop.

kilo closed this issue

2026-10-28 11:26:15 +00:00

Rows
Columns

Record D-083 backlog disposition: re-home excluded wontfix requirements, correct #183/#186 prerequisites #228

Goal

Owner Authorization

Why and Evidence

Registered Successors (this delivery)

Scope

Acceptance Criteria

Constraints

Links