Tasks: Execute / Start buttons, the outcome on the message, the status steps

The last spec artifact. A DAG derived from the design and testing plan; each task names the testing-plan row that proves it. TDD: the test first, red, then green.

Task list

• [x] 1. The config and the renderer — PHASE_SELECTION_MARKER, COMMAND_BUTTONS, BUTTON_NAMES, control_keywords / command_buttons / keyword / command_buttons_for on SlackChannelConfig, expected_commands, render_blocks's commands, render_reply_blocks, say(blocks=), post passing the commands
  • Depends on: none
  • Requirements: R1.1, R1.2, R1.4, R1.5
  • Test: T1 — the config, marker and render tests; T8 — A7
• [x] 2. The press report — report_press on the channel, the two event types in eventlog.py, process_reply carrying url / error, handle_socket_action calling the report on processed
  • Depends on: 1
  • Requirements: R1.3, R2.1–R2.6
  • Test: T1 — the report tests; T8 — A1, A2, A3, A4, A5, A6
• [x] 3. The kickoff's Start button — process_kickoff replying with render_reply_blocks
  • Depends on: 1
  • Requirements: R1.2
  • Test: T2 — the kickoff scenario
• [x] 4. The status line — _button_lines in channels_cmd.py
  • Depends on: 1
  • Requirements: R3.1, R3.2
  • Test: T1 — the status tests
• [x] 5. The scenarios — the four integration scenarios over the socket handlers
  • Depends on: 2, 3
  • Requirements: R1.3, R2.1, R2.2, R2.3, R2.5
  • Test: T2
• [x] 6. Docs, capability docs, decision — the guide, the option and command pages, channels.md, the README and the collaboration reference, the two templates, decision-117 + index row
  • Depends on: 4, 5
  • Requirements: R3.3, R4.1, the capability-docs gate
  • Test: T10 — docs parity; T12 — make check
• [x] 7. Verification — execute testing-plan.md, record evidence/verification.md and evidence/security-review.md
  • Depends on: 5, 6
  • Requirements: all
  • Test: T1, T2, T8, T10, T12, T13

Dependency graph (DAG)

flowchart LR
  T1["1 config + renderer"] --> T2["2 press report"]
  T1 --> T3["3 kickoff Start"]
  T1 --> T4["4 status line"]
  T2 --> T5["5 scenarios"]
  T3 --> T5
  T4 --> T6["6 docs + decision"]
  T5 --> T6
  T5 --> T7["7 verification"]
  T6 --> T7

Checkpoints

After task 1: the render tests green. After task 2: the report tests green. After task 5: T1 and T2 green. After task 6: make check. Then the verification node, the self-review rounds and the security review gate (evidence/security-review.md), then the PR with the reviewer briefing.

Review comments

Appended by the-loop's record-feedback hook when a human gate approves with comments (issue-109). Append-only and attributed: an approval never silently discards a reviewer's suggestions, and the feedback travels with the document it concerns rather than living in a side-channel tracker.