Files
SwiftyandCodex 7dd6e5226d chore(harness): add update-harness skill and CI gate
Summary:
- Add the repo-local update-harness skill and Claude skill symlink.
- Add a Bun-owned ci command and route GitHub CI through it.
- Tighten generated-doc freshness and workspace inventory generation.

Rationale:
- Keeps the harness upgrade workflow available in-repo for future agents.
- Gives local and hosted CI one shared command instead of duplicated YAML.
- Makes generated inventory depend on tracked files and catches real drift.

Tests:
- bun install --frozen-lockfile
- bun run ci

Co-authored-by: Codex <[email protected]>
2026-04-18 22:19:15 +02:00
..
2026-04-17 12:18:09 +02:00

Execution Plans

Plans for multi-step work that spans multiple PRs or sessions. Treat them as checked-in implementation memory that another agent can resume without needing external context.

Active

Active execution plans live in active/. Use them for work that has non-trivial sequencing, tradeoffs, or validation requirements.

See active/ for in-progress plans.

Completed

See completed/ for finished plans and tech-debt-tracker.md for known cleanup work that is not yet an active project.

Plan format

Each plan should include:

  1. Goal — what we're trying to achieve
  2. Steps — ordered list of discrete tasks
  3. Dependencies — what blocks what
  4. Validation — how we know it's done
  5. Decisions — any non-obvious choices future agents must preserve