e2e

Verify board-steward and WorkBoard end-to-end behavior in throwaway test environments.

13|2|Updated May 27, 2026
One-click install
npx skills add https://github.com/malcolm1232/WorkBoard --skill e2e-malcolm1232
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e
Source: https://github.com/malcolm1232/WorkBoard/tree/main/skills/e2e
Command: npx skills add https://github.com/malcolm1232/WorkBoard --skill e2e-malcolm1232

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides a reusable end-to-end test harness for verifying board-steward and WorkBoard behavior without risking pollution of a live board or shared local state.

Core Features & Use Cases

  • Multi-board routing and isolation: Confirms cards land on the correct board and that session-aware board selection stays stable under concurrent writes.
  • Reconciliation and replay safeguards: Tests gating logic, replay-state handling, and no-op paths so startup and recovery behavior stays correct.
  • Real-world regression coverage: Supports both free deterministic checks and an optional real Haiku end-to-end pass for shipped-versus-skipped card outcomes.
  • Use case: Run it after a routing, concurrency, or reconciliation overhaul to verify the system still behaves correctly across isolated throwaway boards.

Quick Start

Ask the Skill to run the appropriate end-to-end test group for your board-steward change, using throwaway boards and live-board safeguards.

Frequently Asked Questions about e2e

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run end-to-end regression tests for board-steward routing without touching a live board?

End-to-end regression tests for board-steward routing use throwaway boards and live-board count guards to verify multi-board routing and session isolation without polluting live boards or shared local state. Tests run via subprocess-based deterministic execution.

What is session isolation testing for multi-board WorkBoard routing?

Session isolation testing confirms cards land on the correct board and that session-aware board selection stays stable under concurrent writes. This ensures multi-board routing behavior remains correct when multiple sessions interact with WorkBoard simultaneously.

How does reconciliation gating and replay handling work in board-steward end-to-end tests?

Reconciliation gating and replay handling tests verify gating logic, replay-state handling, and no-op paths so startup and recovery behavior stays correct. They ensure reconciliation safeguards prevent duplicate or erroneous card operations during recovery workflows.

Can I validate shipped versus skipped card outcomes with real Haiku validation in end-to-end tests?

Real Haiku validation is an optional end-to-end pass that validates shipped-versus-skipped card outcomes in throwaway test environments. It complements free deterministic checks by providing real-world regression coverage for board-steward behavior.

When should I use an end-to-end test harness for board-steward reconciliation and concurrency changes?

Use an end-to-end test harness after a routing, concurrency, or reconciliation overhaul to verify the system still behaves correctly across isolated throwaway boards. It catches regressions in multi-board routing, session isolation, and replay safeguards.

What safeguards are needed to prevent live board pollution during WorkBoard end-to-end testing?

Live board pollution prevention requires temporary state isolation, live-board count guards, and subprocess-based execution in throwaway test environments. These safeguards ensure deterministic and recovery workflows never touch shared local state or live boards.