llama-atmosphere-agent: four open reproductions are green now, so they stop being records

[bernardladenthin]

Summary

• Four @Disabled reproductions pass now, so they stop being records. Asked what was still open, I measured it rather than reading the annotations: of the eight disabled cases in ScreenUseCasesTest, four are green. A record of something that is no longer true is worse than no record.
• None of them was aimed at. They fell out of the console folding its own output, the settled width change wiping and reprinting instead of repairing row by row, and the changes carried against JLine — all merged in llama-atmosphere-agent: make the pinned console survive a window resize #462.
• Each keeps a note saying what it used to record and why it is green, so the history survives the annotation.

test	what it used to record
draggingNarrowerKeepsTheEditLine	a "known defect" for most of the investigation: narrowing lost the edit line
draggingWiderWithAThreeRowBlock	rule three columns short, state row shifted one column, prompt on two rows
thePromptItselfStaysVisibleAfterEnlarging	OPEN for four rounds: block exactly right, prompt's row blank
afterATurnShrinkingAndGrowingKeepsOneRuleNoWiderThanTheWindow	OPEN: shrinking and growing left a rule wider than the window

Four remain disabled, and each is still true: three astral-glyph cases (an emoji is a surrogate pair and breaks the pinned region's column arithmetic) and the shrinking-window prompt drift, where the prompt would have to move up and nothing a caller can emit does that without breaking the reader's cursor bookkeeping.

Test plan

• Affected unit / integration tests pass locally
• CI is green on this branch
• Docs / CHANGELOG updated where applicable

ScreenUseCasesTest: 57 tests, 0 failures, 4 skipped — green three times in a row against -Djline.version=4.4.6-atmosphere. Three runs rather than one because this class has a flakiness history, and enabling a test that passes four times in five would be worse than leaving it off.

No production code changes; this is test annotations and comments only.

Related issues / PRs

Follows #462, which is what made these four pass.

Checklist

• I have read CONTRIBUTING.md and CODE_OF_CONDUCT.md
• My commits follow Conventional Commits
• No security-sensitive changes (if there are, I have notified the maintainer privately per SECURITY.md)

Two boxes left open deliberately: CI has not run on this branch yet, and the commit subject follows the surrounding history's pattern (llama-atmosphere-agent: …) rather than test:/fix: — say the word and I will rewrite it.

🤖 Generated with Claude Code

https://claude.ai/code/session_01E2h8gXyyE5UeimkL9vQv9G

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud