e2e probe: identify the single syntax-colored span in a plain-text editor — editor-features:137 (#229 follow-up)

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.

CODE-363

@codex

🤖 Agent note · parked

Agent: queue worker (repo-worker-code), lane F shift
Session / ID: queue task 4682, lane F, 2026-10-31
Found via: queue claim (resume)
Task: Re-checked PR 3217 @74d15872: diff verified on-intent (one test-file change excluding collab-cursor spans from coloredSpanCount), CodeRabbit pass, 0 review threads, no hard-stop labels. No GitHub Actions CI exists for pkgs/id PRs by design (id-check.yml triggers on push to main + nightly, not pull_request) — verification stands on the prior lane's laptop Firefox e2e 47/47 at this sha. I re-requested a Codex review (@codex review, 23:21:04Z); Codex replied at 23:21:16Z that code-review usage limits are still reached — zero findings have ever been posted on this PR. Parked 60m on the Codex gate rather than merging past an unrun review.
Expectation: resume = trigger @codex review once limits reset; a clean review → merge and close e2e probe: identify the single syntax-colored span in a plain-text editor — editor-features:137 (#229 follow-up) #1229.
Links: PR test(id): exclude collab-cursor spans from plain-text highlight count (#1229) #3217

You have reached your Codex usage limits. You can see your limits in the Codex usage dashboard.

🤖 Agent note · picked up

Agent: queue worker (repo-worker-code), lane A shift
Session / ID: queue task 4682, lane A, resumed 2026-10-31
Found via: queue claim (resume — PR 3217 @74d15872 verified 47/47 Firefox e2e on laptop by prior lanes; parked only on the Codex gate after Codex reviews failed on usage limits with zero findings)
Task: Trigger a fresh Codex review on PR 3217 (usage limits reported reset ~00:03Z, evidenced by a clean completed review on PR 3251); if the review completes clean and the diff still matches intent, merge and close e2e probe: identify the single syntax-colored span in a plain-text editor — editor-features:137 (#229 follow-up) #1229; otherwise re-park naming the blocker.
Expectation: effort S; done = PR 3217 merged and e2e probe: identify the single syntax-colored span in a plain-text editor — editor-features:137 (#229 follow-up) #1229 closed, or a re-park with the exact Codex state.
Links: PR test(id): exclude collab-cursor spans from plain-text highlight count (#1229) #3217 · branch queue/4682-1229-collab-cursor-span-exclusion

test(id): exclude collab-cursor spans from plain-text highlight count (…

🤖 Agent note · done

Agent: queue worker (repo-worker-code), lane A shift
Session / ID: queue task 4682, lane A, 2026-10-31
Found via: queue claim (resume from park on the Codex gate)
Task: Codex usage limits had reset (clean completed review on PR 3251 ~00:03Z per lane handoff). Re-requested review on PR 3217 @74d15872 at 00:32:27Z; Codex completed clean at 00:33:48Z ("Didn't find any major issues"), 0 review threads. Diff re-verified fresh as the single decoration-scoped test change; CodeRabbit SUCCESS; no Actions CI exists for pkgs/id PRs by design — verification stands on the prior lanes' laptop Firefox e2e 47/47 at this sha. Merged.
Expectation: done = PR 3217 merged, e2e probe: identify the single syntax-colored span in a plain-text editor — editor-features:137 (#229 follow-up) #1229 closed. Met.
Links: PR test(id): exclude collab-cursor spans from plain-text highlight count (#1229) #3217 · merge e08fceb48e42faeae62fc4fccc3d53871fab5731

Navigation Menu

Repository navigation

e2e probe: identify the single syntax-colored span in a plain-text editor — editor-features:137 (#229 follow-up) #1229

Acceptance criteria

42 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

e2e probe: identify the single syntax-colored span in a plain-text editor — editor-features:137 (#229 follow-up) #1229

Description

Acceptance criteria

Activity

developing-today commented on Oct 27, 2026

42 remaining items

dezren39 commented on Oct 31, 2026

chatgpt-codex-connector commented on Oct 31, 2026

dezren39 commented on Nov 1, 2026

dezren39 commented on Nov 1, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions