Plan #288: GitHub-style runner design #304
No reviewers
Labels
No labels
actions
bug
cli
duplicate
enhancement
fork
forum
git storage
help wanted
insights
invalid
issues
moderation
oidc
ownership transfer
packages
pr/merge protection rules
projects
pull requests
question
releases
sponsorships
tags
webhooks
wiki
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
crueber/walhub!304
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/issue-288"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Design plan for #288 (docs only, no implementation until reviewed).
New: docs/features/12_runner.md — researched runner plan with numbered decisions D1–D8 (pull-based model, bucket-native CAS queue, long-poll claim + leases, art_/wrt_/wjt_ tokens, in-repo workflows, secretbox secrets, checks/logs/artifacts reporting, security caps, R1/R2/R3 rollout slices), prior-art research (GHA protocol, act_runner, Woodpecker), testing strategy, non-goals + open questions Q1–Q6 for Chris. No law-1 amendment proposed (reserve container draft in §10). Linked from docs/features/README.md table.
Acceptance: plan covers runner model + protocol, job format + triggers, execution/isolation, secrets, checks integration, logs, artifacts, security caps, UI, testing, non-goals; ends with awaiting-review marker naming Chris; zero code changes (git status: 1 new doc + 1 README table row).
Do NOT merge until the plan itself is reviewed — implementation waits on #288 approval.