Sync README with current ZMK configuration (v0.3, unified hold-tap, nice-luffy-wanted)

[Copilot]

README documentation was stale and described removed features. Configuration files were already correct.

Changes

Home Row Mod Behavior

• Removed documentation of obsolete two-behavior system (Standard/Strict timing with separate shift behaviors)
• Documented actual unified ht behavior with hold-trigger-on-release and all 42 key positions configured
• Added require-prior-idle-ms=150 and release-order handling details

Before:

Standard timing for Ctrl, Alt, GUI (280ms)
Strict timing for Shift (300ms, tap-preferred)

Now:

Unified ht behavior for all modifiers (280ms balanced)
hold-trigger-on-release: fixes release-order sensitivity
hold-trigger-key-positions: all 42 keys (enables same-hand combos)

Display Configuration

• Added nice-luffy-wanted module documentation (was undocumented)
• Documented display build variants vs plain builds
• Noted ZMK v0.3 pinning

Troubleshooting

• Added hardware fix guide link for Mill-Max socket issues
• Added home row mod tuning parameters reference

Original prompt

[Chronological Review] 1. Initial request: User asked to check ZMK config and pin ZMK version based on a blog post 2. Pinned ZMK to v0.2 in west.yml and build.yml, committed and pushed 3. Reviewed Zephyr 4.1 blog post for future upgrade requirements (v0.4), decided to wait 4. Created implementation plan for home row mod fixes and display customization 5. Implemented positional hold-tap for shift keys (ht_shift_l/ht_shift_r), upgraded to v0.3, added nice-view-gem module 6. User reported issues: D+V, J+I not working, wanted to switch display to nice-luffy-wanted 7. Root cause analysis: positional hold-tap blocked same-hand shift; global-quick-tap too aggressive; release-order sensitivity 8. Implemented fix: unified ht behavior with hold-trigger-on-release + all 42 key positions, switched to nice-luffy-wanted 9. User asked about Enter/Esc not working in games — explained USB boot protocol + layer-tap interaction 10. User asked about display showing current layer — checked nice-luffy-wanted source, confirmed it does NOT show layers 11. User reported hardware issue: column 5 intermittent failures on display Corne (Mill-Max sockets) 12. Created hardware fix guide markdown file and committed to repo

[Intent Mapping]

• Pin ZMK version (completed, now on v0.3)
• Fix home row mod misfires (multiple iterations, final: hold-trigger-on-release with all positions)
• Add custom nice!view display (switched from gem to luffy-wanted)
• Understand Enter/Esc issue in games (explained, no code change needed)
• Check if display shows layers (checked, it doesn't)
• Diagnose and document hardware column fix (created guide)

[Technical Inventory]

• ZMK firmware v0.3 (pinned), previously v0.2, originally main
• Nice!nano v2 board, Corne keyboard (6-column, 42 keys)
• nice-luffy-wanted display module (whoop-t/nice-luffy-wanted, revision: main)
• Hold-tap behavior: balanced flavor, hold-trigger-on-release, hold-trigger-key-positions (all 42), require-prior-idle-ms=150
• USB boot protocol enabled (CONFIG_ZMK_USB_BOOT=y)
• Mill-Max hot-swap sockets for nice!nano
• Two Corne keyboards: one with nice!view display, one without

[Code Archaeology]

• config/west.yml: remotes zmkfirmware + whoop-t, projects zmk v0.3 + nice-luffy-wanted main
• .github/workflows/build.yml: uses @v0.3
• build.yaml: 5 builds (corne_left, corne_right, corne_left+nice_luffy_wanted, corne_right+nice_luffy_wanted, settings_reset)
• config/include/behaviors.dtsi: single ht behavior with hold-trigger-on-release + all positions
• config/corne.keymap: all home row mods use &ht, 9 layers, combos for esc/enter
• config/corne.conf: USB boot protocol, BT power, no display config (display handled by shield)
• docs/column-fix-guide.md: hardware troubleshooting guide

[Progress Assessment]

• ZMK version pinning: DONE (v0.3)
• Home row mod fix: DONE (hold-trigger-on-release approach, user says "not 100% but improved")
• Display module: DONE (nice-luffy-wanted)
• Enter/Esc in games: EXPLAINED (no code change)
• Layer display: ANSWERED (nice-luffy-wanted doesn't show layers)
• Hardware column fix guide: DONE (committed to repo)

[Context Validation]
All file states, config decisions, and user preferences are captured. The user has two Corne keyboards, the display one has hardware issues. Home row mods are improved but not perfect — acknowledged as a ZMK limitation.

[Recent Commands Analysis]

• Last commands: Created docs/column-fix-guide.md with comprehensive hardware fix guide, then git add/commit/push
• The push was successful: commit 423db65, pushed to master
• The guide covers three options: reflow solder, clean/reseat, swap test
• This was triggered by user asking for a "pretty md file" for the hardware fix options

1. Conversation Overview: - Primary Objectives: (1) Pin ZMK firmware version, (2) Fix home row mod misfires ("hold f is the Lshift, if i want to type capital N, i can hold f and press n... sometime it will output fn instead of N"), (3) Customize nice!view display, (4) Diagnose hardware column failures on display Corne keyboard - Session Context: Started with ZMK version pinning, evolved through multiple iterations of home row mod tuning (positional hold-tap → unified hold-trigger-on-release), display module selection (nice-view-gem → nice-luffy-wanted), and culminated in hardware troubleshooting for intermittent column 5 failures - User Intent Evolution: Initially focused on firmware config, then shifted to keyboard usability (HRM misfires), then display customization, and finally hardware diagnosis

2. Technical Foundation:
   • ZMK Firmware: Pinned to v0.3 (upgraded from main → v0.2 → v0.3 for nice-view-gem compatibility)
   • Board: nice!nano v2 with Mill-Max hot-swap sockets
   • Keyboard: Corne 6-column split (42 keys), two pairs — one with nice!view display, one without
   • Display Module: whoop-t/nice-luffy-wanted (revision: main) — shows battery, BT profile, Luffy art; does NOT show current layer
   • Build...

Created from Copilot CLI via the copilot delegate command.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.