Skip to content

Backlog: record the 2026-09-12 batch - #506

Merged
iamfatness merged 1 commit into
mainfrom
docs/backlog-2026-09-12-batch
Sep 12, 2026
Merged

iamfatness merged 1 commit into
mainfrom
docs/backlog-2026-09-12-batch

Conversation

@iamfatness

Copy link
Copy Markdown
Owner

Nine items closed and two partial, all shipped in beta-2026-09-12-e1223d3, none live-checked.

T1.12 #475 join-time prompts answered #493
T1.13 #473 media decoder failures are loud #494 — observability only
T2.6 #438 packaging spec reconciled #504
T2.7 #474 one shortcut, uninstall cleans up #497
T2.8 #469 recordings resolve absolute #496
T2.9 #466 recording lifecycle survives a stream #499
T2.10 #468 sender health stops lying #499
T3.2 #440 WebView2 message #504
T3.7 #470 ISOs armed with capture off warn #502
T3.8 #482 ISO frames conform to the writer #503
T2.1 #433 partial — WER dumps are HKLM-only
T3.5 #476 partial — the rest is a product call

Each row keeps the thing that's expensive to rediscover rather than just a tick: T2.8 records that the issue's premise was wrong, T3.8 records that its end-to-end test is a guard passing either way, T2.6 records that dropping MSIX cost auto-update, and T2.1 records the measurement proving a per-user installer cannot enable crash dumps.

Tier 1 now has one open item, waiting on a decision rather than effort. T1.11 step 1 needs a change to the Take path itself, because a plain cut never captures the outgoing scene — written into the row so the next session doesn't rediscover it and ship it blind.

Two entries came from the work rather than the list: #505 (per-layer border controls are vestigial — the core forces borderStyle="none" on every route layer) and the T1.11 ruling.

The header now says the honest thing: the binding constraint is T0.1 and a live check, not engineering capacity.

🤖 Generated with Claude Code

https://claude.ai/code/session_014yuH7EMvWCWdkhvevrtMyJ

Nine items closed and two partial, all shipped in beta-2026-09-12-e1223d3 and
none of them live-checked:

  T1.12 #475  join-time prompts answered            #493
  T1.13 #473  media decoder failures are loud       #494  (observability ONLY)
  T2.6  #438  packaging spec reconciled             #504
  T2.7  #474  one shortcut, uninstall cleans up     #497
  T2.8  #469  recordings resolve absolute           #496
  T2.9  #466  recording lifecycle survives a stream #499
  T2.10 #468  sender health stops lying             #499
  T3.2  #440  WebView2 message                      #504
  T3.7  #470  ISOs armed with capture off warn      #502
  T3.8  #482  ISO frames conform to the writer      #503
  T2.1  #433  PARTIAL — WER dumps are HKLM-only
  T3.5  #476  PARTIAL — the rest is a product call

Each row keeps the thing that is expensive to rediscover rather than just a tick:
T2.8 records that the issue's premise was wrong (the default was already
absolute; a persisted relative preference bypassed it), T3.8 records that its
end-to-end test is a guard which passes either way, T2.6 records that dropping
MSIX cost auto-update, and T2.1 records the measurement proving a per-user
installer cannot enable crash dumps.

Tier 1 now has ONE open item, and it is waiting on a decision rather than
effort: T1.11 step 1 needs a change to the Take path itself, because a plain cut
never captures the outgoing scene. That is written into the row so the next
session does not rediscover it and ship it blind.

Two entries came out of the work rather than the list: #505 (the per-layer
border controls are vestigial — the core forces borderStyle="none" on every
route layer, so they cannot do anything) and the T1.11 ruling.

The honest header: the binding constraint is now T0.1 and a live check, not
engineering capacity.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_014yuH7EMvWCWdkhvevrtMyJ
@iamfatness
iamfatness merged commit b381092 into main Sep 12, 2026
10 checks passed
@iamfatness
iamfatness deleted the docs/backlog-2026-09-12-batch branch September 12, 2026 16:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants