Description
Follow-up to #229, from queue task 1240's classification of the isolated Firefox dispatch run 40402931464 (PR #987 branch).
pkgs/id/e2e/tests/editor-features.spec.ts:137 "plain text file has no syntax highlighting" fails deterministically (attempt + retry #1): after typing This is plain text with no highlighting. into a .txt file and settling 2s, coloredSpanCount is 1, expected 0 — exactly one span[style] with a style.color inside #editor .ProseMirror.
The CI job log cannot identify the span (Playwright's error-context.md is not in the job log), so this is unresolved: a Shiki/highlight leak into rich-mode text (product bug) vs an editor decoration span the test should not count (test artefact). All other syntax-highlighting tests in the spec pass.
Acceptance criteria
- The single colored span is identified from a live isolated run (outerHTML, class, ancestor chain) and recorded on this issue.
- Verdict recorded: product highlight leak (with mechanism → fix packet) or named editor decoration (with the locator exclusion the test needs).
- Probe only in the first pass — no code/test changes until the span is identified.
Evidence pack: goal hidden_files/probe-2026-10-27-t1240/failures.txt (failure block editor-features 1), classification comment on #229 by queue task 1240.
Activity
developing-today commentedon Oct 27, 2026
CODE-363
42 remaining items
dezren39 commentedon Oct 31, 2026
🤖 Agent note · parked
chatgpt-codex-connector commentedon Oct 31, 2026
You have reached your Codex usage limits. You can see your limits in the Codex usage dashboard.
dezren39 commentedon Nov 1, 2026
🤖 Agent note · picked up
queue/4682-1229-collab-cursor-span-exclusiontest(id): exclude collab-cursor spans from plain-text highlight count (…
dezren39 commentedon Nov 1, 2026
🤖 Agent note · done
e08fceb48e42faeae62fc4fccc3d53871fab5731