docs/slate-v2/ledgers/issue-dossier-pilot-5.md
This is a five-issue pilot for the compiled issue dossier workflow. It uses the frozen issue ledger, targeted live GitHub reads, and current local Slate v2 proof references. No GitHub comments, labels, or closure actions were written.
gitcrawl was unavailable in this environment, so related-thread discovery falls
back to the frozen ledger, local issue corpus, and targeted live GitHub reads.
Status: improves-claimed Bucket: already-accounted Confidence: high
Issue summary: This is a performance issue about repeated exact-path tree updates needing a batch-aware apply engine. The live issue is open, references PR #6039, and asks for a benchmark-backed architecture improvement rather than a single UI bug fix.
Evidence:
transactionality-and-batch-engine, valid, severe,
improves-claimed..tmp/slate-v2/scripts/benchmarks/core/current/transaction-execution.mjs;
docs/slate-v2/slate-tranche-3-execution.md;
docs/slate-v2/ledgers/issue-coverage-matrix.md.Decision:
Keep this as improves-claimed, not fixes-claimed. Slate v2 has
transaction/applyOperations benchmark coverage for mixed structural snapshots,
but the current ledger does not define an accepted performance threshold that
would prove the full upstream benchmark claim.
PR-description text: Improves #6038: Slate v2 adds transaction/applyOperations benchmark coverage for batch-style repeated tree updates, but this PR does not auto-close the issue because no accepted performance threshold proves the full upstream benchmark claim.
Status: cluster-synced Bucket: v2-dom-selection Confidence: medium
Issue summary: This is a DOM selection/navigation bug at a table boundary when the table is the last node in the editor. The live issue is open and gives official table-example repro steps for arrow-key movement at the end of the document.
Evidence:
dom-selection-synchronization, likely-valid, cluster-synced.bug label..tmp/slate-v2/packages/slate-dom/test/bridge.ts;
.tmp/slate-v2/packages/slate-dom/test/dom-coverage.ts;
docs/plans/2026-05-04-slate-v2-full-issue-ledger-architecture-ralplan.md;
docs/plans/2026-05-04-slate-v2-full-issue-ledger-architecture-ralplan-issue-matrix.md.Decision:
Keep this as cluster-synced. The architecture owner is the DOM
selection/focus bridge, but the exact table-edge browser reproduction is not
proved end to end yet. Do not auto-close.
PR-description text: Related #6034: covered as DOM selection/focus bridge pressure; exact table-edge browser repro is not auto-closed.
Status: cluster-synced Bucket: v2-input-runtime Confidence: high
Issue summary:
This is an Android input/composition bug where toggling a mark on a collapsed
selection causes keyboard dismissal and selection jumps while typing. The live
issue is open, has bug and cross-platform labels, and includes reporter
comments with Android WebView context and operation logs.
Evidence:
mobile-ime-and-selection-sync, valid, cluster-synced.bug and cross platform; comments
include operation logs.docs/plans/2026-05-04-slate-v2-full-issue-ledger-architecture-ralplan.md;
docs/plans/2026-05-04-slate-v2-full-issue-ledger-architecture-ralplan-issue-matrix.md;
docs/slate-issues/requirements-from-issues.md#r7-make-input-composition-and-ime-semantics-first-class.Decision:
Keep this as cluster-synced. Slate v2 should route it through the shared
input/composition/mobile runtime, but exact closure requires Android/device proof
for the mark-toggle collapsed-selection repro.
PR-description text: Related #6022: Slate v2 input/composition runtime targets the Android mark-toggle selection/keyboard class, but this PR does not auto-close without matching device proof.
Status: triage-closed Bucket: skip-invalid Confidence: high
Issue summary: This reports two Slate editors rendering the same value object reference and breaking DOM/path resolution. The live issue is open, but maintainer discussion clarifies that sharing the same Slate node objects across editor instances is not a supported contract because editor DOM/path maps are keyed by node identity.
Evidence:
shared-node-identity-across-editors, likely-invalid,
triage-closed.bug label.docs/plans/2026-05-04-slate-v2-full-issue-ledger-architecture-ralplan.md;
docs/plans/2026-05-04-slate-v2-full-issue-ledger-architecture-ralplan-issue-matrix.md.Decision: Do not claim this as a v2 fix. Raw Slate should not support the same node object identity mounted in multiple editor runtimes as a normal contract. Reopen only if a current minimal repro shows a supported usage failing.
PR-description text: None; detailed ledger only. #6016 is classified as likely-invalid shared-node identity misuse, not a Slate v2 closure claim.
Status: fixes-claimed Bucket: already-accounted Confidence: high
Issue summary:
This is an API ergonomics issue asking React providers to accept an already
initialized editor without requiring a separate provider-level initialValue.
The live issue is open, and the current Slate v2 coverage matrix already carries
the exact fix claim.
Evidence:
react-initialization-api-ergonomics, valid, fixes-claimed.improvement label.docs/slate-v2/ledgers/issue-coverage-matrix.md;
docs/slate-v2/references/pr-description.md;
.tmp/slate-v2/packages/slate/test/state-tx-public-api-contract.ts.Decision:
Keep the exact Fixes #6013 claim. Slate v2 makes editor initialization own the
initial value, so the React provider can accept a pre-initialized editor without
requiring another initialValue prop.
PR-description text: Fixes #6013: React providers accept pre-initialized editor instances without a provider-level initialValue; editor state is seeded during editor creation.