0 Fork 0

mirror of https://github.com/kevinveenbirkenbach/computer-playbook.git synced 2026-11-11 21:26:44 +00:00

Files

T

kevinveenbirkenbach da140094a1 docs(agents): split iteration loops and refactor Playwright SPOT

Split docs/agents/action/iteration.md into role.md, playwright.md,
workflow.md, and a scope-focused README. Move Certificate Authority
and Inspect rules into role.md. Rewrite playwright.md as a machine-
oriented state machine with explicit preconditions, procedure, exit
gates, and escape path.

Extract Playwright spec content MUSTs into the new contrib SPOT
docs/contributing/artefact/files/role/playwright.specs.js.md. Reduce
the agent-side spec and env.j2 pages to procedure only. Align the
framework SPOT and the test-e2e-playwright role README with the
central templates/package.json.j2 + files/playwright.config.js model
and images.playwright.version as single source of truth.

Sweep em dashes and sentence-case role headings across all touched
docs per documentation.md and readme_md.md rules.

2026-04-19 22:04:24 +02:00

1.7 KiB

Raw Blame History

Workflow Loop

Use this page for iterating on GitHub Actions workflows locally through Act. For role-level and spec-level iteration, see Role Loop and Playwright Spec Loop.

Rules

When you are developing, optimizing, or debugging GitHub Actions workflows, you SHOULD explicitly propose make act-workflow as the default iterative local debug loop.
You MUST NOT assume that Act should be used automatically for workflow work. If the user agrees with the proposal, you SHOULD use make act-workflow for the iteration loop.
After the user agrees to use Act, you SHOULD rerun make act-workflow after each focused workflow change and inspect the new output before making further edits.
If the workflow uses a distro matrix, you MUST iterate on one distro at a time instead of rerunning the whole matrix during the default debug loop.
Debian SHOULD be the preferred distro for that focused workflow iteration unless the failure is clearly distro-specific or the user asked for a different distro.
When you constrain an Act matrix run through ACT_MATRIX, you MUST use Act's key:value syntax instead of key=value. Otherwise Act may ignore the filter and rerun the whole matrix.
For .github/workflows/test-environment.yml, the preferred focused Debian example is make act-workflow ACT_WORKFLOW=.github/workflows/test-environment.yml ACT_JOB=test-environment ACT_MATRIX='dev_runtime_image:debian:bookworm'.
You SHOULD avoid jumping straight to repeated remote CI reruns when make act-workflow can validate the workflow locally and the user agreed to use it.
You MAY widen the scope to make act-app or make act-all when the problem spans more than one workflow or make act-workflow is too narrow for the failure.

1.7 KiB Raw Blame History

Workflow Loop

Rules

1.7 KiB

Raw Blame History