NS9 slice: Add terminal color-mode probes and accessibility guardrails #63
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
OBJECTIVE:
mimchooses safe color output for the current terminal and has guardrails that prevent unreadable or color-only UI states.AUTHORITY: Parent #57; newed
adapt.rs/detect.rs; mim PRODUCT.md mobile-first terminal constraint; req: ui/001-002, governance/001-002, testing/001-004.AGENT AUTHORITY:
PARENT: #57 via explicit issue link and parent checklist.
SCOPE: Terminal capability detection/override-by-build-profile if already conventional, fallback strategy, contrast/readability tests for key token pairs, no-color behavior, style reset audit.
BOUNDARIES: Do not add runtime config files or a broad settings system. Environment probing must be deterministic and safe in SSH/non-interactive tests.
ACCEPTANCE:
VERIFICATION:
zig build testzig build v1-smokeBLOCKERS: none.
Closing receipt for #63.
Implemented in local commit
de3b5d4(Detect terminal color capabilities):src/theme.zigfor truecolor, 256-color, 16-color, and mono modes.TERM,COLORTERM,NO_COLOR,MIM_COLOR,COLORFGBG) without config files or installers.Verification:
zig build✅zig build test✅zig build terminal-e2e✅zig build run -- --help✅zig build --prefix /tmp/mim-install verify-install-code✅redgate list /opt/repositories/mim/REQUIREMENTS.md && redgate lint /opt/repositories/mim/REQUIREMENTS.md && redgate health /opt/repositories/mim/REQUIREMENTS.md✅