Implement telegraph display showing all pending delayed actions to opponents

## Metadata - **Commit Message**: `feat(combat): implement telegraph display for pending delayed actions` - **Branch**: `feature/m4-telegraph-display` ## Background and Context The telegraph system shows all pending delayed actions to all combatants. This allows opponents to plan counters — if they see a heavy overhead strike arriving in 2 rounds, they can position a block or dodge. The display shows action name, source combatant, target cells, and rounds remaining. ## Expected Behavior The combat screen displays a "Pending Actions" section listing all delayed actions in the queue. Each entry shows: combatant name, action name, target pattern (highlighted cells on the grid), and rounds until execution. ## Acceptance Criteria - [ ] All pending delayed actions are visible to all combatants - [ ] Display shows: source combatant, action name, rounds remaining - [ ] Target cells are highlighted on the body grid preview - [ ] Display updates each round as countdowns change - [ ] Newly committed delayed actions appear immediately in the telegraph ## Subtasks - [ ] Code: Implement `telegraph_data()` method on TurnManager returning list of pending action info - [ ] Code: Format telegraph display as part of combat screen output - [ ] Code: Highlight target cells on the body grid in the combat display - [ ] Code: Update telegraph display after each Countdown phase - [ ] Docs: Update YARD comments on affected classes and methods. Update relevant Docusaurus documentation pages if applicable. - [ ] Tests (Cucumber): Add `tests/unit/telegraph_display.feature` covering telegraph shows correct pending actions, countdown updates, cell highlighting. - [ ] Tests (Cucumber Integration): Add integration feature in `tests/integration/` for telegraph visible to both combatants during multi-round combat. - [ ] Tests (Profiling): Run `bundle exec rake unit_profile` and verify no performance regressions. - [ ] Quality: Verify coverage >=97% via `bundle exec rake unit`. If coverage is <97% then review the current unit test coverage report at `build/tests/unit/coverage/` and use it to write new Cucumber based unit tests to improve code coverage. Specifically, write Cucumber/Gherkin style unit tests that are descriptively named and specifically improve coverage on whichever file has the most uncovered lines by writing tests that will target the uncovered lines in the report. Once that is done rerun `bundle exec rake unit` to verify all tests pass and coverage is above >=97%. Only mark this as complete once coverage is >=97%, if not repeat this task as many times as is needed until coverage reaches >=97%. - [ ] Quality: Run `bundle exec rake` (default task: unit tests with coverage) and `bundle exec rake integration`, fix any errors if needed ensuring both pass across **entire** code base, do not ignore any failure even if it seems unrelated to this commit, fix it. ## Definition of Done This issue is complete when: - All subtasks above are completed and checked off. - A Git commit is created where the **first line** of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation. - The commit is pushed to the remote on the branch matching the **Branch** in Metadata exactly. - The commit is submitted as a **pull request** to `master`, reviewed, and **merged** before this issue is marked done.

freemo commented

2026-03-16 01:50:11 +00:00

Owner

Metadata

Commit Message: feat(combat): implement telegraph display for pending delayed actions
Branch: feature/m4-telegraph-display

Background and Context

The telegraph system shows all pending delayed actions to all combatants. This allows opponents to plan counters — if they see a heavy overhead strike arriving in 2 rounds, they can position a block or dodge. The display shows action name, source combatant, target cells, and rounds remaining.

Expected Behavior

The combat screen displays a "Pending Actions" section listing all delayed actions in the queue. Each entry shows: combatant name, action name, target pattern (highlighted cells on the grid), and rounds until execution.

Acceptance Criteria

All pending delayed actions are visible to all combatants
Display shows: source combatant, action name, rounds remaining
Target cells are highlighted on the body grid preview
Display updates each round as countdowns change
Newly committed delayed actions appear immediately in the telegraph

Subtasks

Code: Implement telegraph_data() method on TurnManager returning list of pending action info
Code: Format telegraph display as part of combat screen output
Code: Highlight target cells on the body grid in the combat display
Code: Update telegraph display after each Countdown phase
Docs: Update YARD comments on affected classes and methods. Update relevant Docusaurus documentation pages if applicable.
Tests (Cucumber): Add tests/unit/telegraph_display.feature covering telegraph shows correct pending actions, countdown updates, cell highlighting.
Tests (Cucumber Integration): Add integration feature in tests/integration/ for telegraph visible to both combatants during multi-round combat.
Tests (Profiling): Run bundle exec rake unit_profile and verify no performance regressions.
Quality: Verify coverage >=97% via bundle exec rake unit. If coverage is <97% then review the current unit test coverage report at build/tests/unit/coverage/ and use it to write new Cucumber based unit tests to improve code coverage. Specifically, write Cucumber/Gherkin style unit tests that are descriptively named and specifically improve coverage on whichever file has the most uncovered lines by writing tests that will target the uncovered lines in the report. Once that is done rerun bundle exec rake unit to verify all tests pass and coverage is above >=97%. Only mark this as complete once coverage is >=97%, if not repeat this task as many times as is needed until coverage reaches >=97%.
Quality: Run bundle exec rake (default task: unit tests with coverage) and bundle exec rake integration, fix any errors if needed ensuring both pass across entire code base, do not ignore any failure even if it seems unrelated to this commit, fix it.

Definition of Done

This issue is complete when:

All subtasks above are completed and checked off.
A Git commit is created where the first line of the commit message matches the Commit Message in Metadata exactly, followed by a blank line, then additional lines providing relevant details about the implementation.
The commit is pushed to the remote on the branch matching the Branch in Metadata exactly.
The commit is submitted as a pull request to master, reviewed, and merged before this issue is marked done.