docs(ledger): record the 2026-10-12 Safari fixes on #9Z197J

Merged
BI
1mo ago
+12-0

User description

Summary

  • Before: ledger row #9Z197J still said all eight WebKit failures were open and unexamined.

  • After: a queued inbox update records what happened today. WebKit now runs in CI (#3487), and its genuine failures were fixed on the test side in #3492-#3494 and #3501-#3504. The last three failures were the same race: a keypress fired before React had attached the handler. The row names the helper to use for that, and the one remaining check, which is to read the first main run after #3504.

  • Ledger-only: one inbox request file. It reconciles into docs/outstanding-issues.md after merge.

Verification

  • Checks run: npm run check:outstanding-issues ("Outstanding-issues guard passed: 858 rows") and prettier --check on the inbox file, both clean.

Risk and rollout

  • Risk: none. Docs only.
  • Rollback: revert this commit.
  • Provider or production effects: None.

Notes

  • Ledger: #9Z197J.

🤖 Generated with Claude Code

https://claude.ai/code/session_01DCghuougzFFXRF3dQQEcYr

Generated by Claude Code

CodeAnt-AI Description

Update Safari CI failure tracking and next verification step

What Changed

  • Records that WebKit/Safari now runs in CI and that the failures it exposed were fixed in tests without skipping or weakening checks.
  • Identifies the remaining intermittent failures as interactions happening before the page is ready and names the next run to check.
  • Clarifies that the browser job is not required for pull requests and does not block merges.

Impact

✅ Clearer Safari test status
✅ Easier identification of page-readiness test races
✅ Clearer post-fix verification

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

Summary by cubic

Updates ledger row #9Z197J to record the 2026-10-12 WebKit/Safari fixes.

The queued inbox request reconciles into docs/outstanding-issues.md after merge. Previously the row listed all eight WebKit failures as open and unexamined; it now notes WebKit runs in CI (#3487), the genuine failures were fixed test-side in #3492-#3494 and #3501-#3504, and the last three were the same race — a keypress fired before React attached the handler. The row names expectHydrated as the helper to use and leaves one remaining check: read the first main run after #3504.