chore: set up how we work: roles, skills, hooks, Go scaffold, CI, Renovate #14
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/project-setup"
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?
Summary
Sets up how lazyforge gets built: roles, the ticket → composer → merge flow, project skills and hooks, a Go scaffold with CI, and Renovate onboarding. Also records the PM's install and update requirements in the design.
What's in it
product-voice(loaded every session),engineering-decision,go-development,comment-standard,ticket-workflow,ticket-kickoff(routes to composer / composer-lite / inline),ship-it.go-development(pluscomment-standardfor production Go) has been loaded, and there's a reminder to run ship-it after inline work. Hook test suite:50 passed, 0 failed.make check(format check, golangci-lint v2, race tests, build),.golangci.yml, CI on PRs and pushes to develop/main.renovate.jsontargetingdevelop, withopus/sonnetdriver labels (validated:Config validated successfully).Verification
make check:0 issues.from lint; tests pass (no test files yet); build ok.golangci-lint config verify: ok.Backlog
Tickets #1–#13 are filed: three spikes, the v1 features, release/install (#11), the update check (#12), and the product decisions that need the PM (#13).
Decisions
ubuntu-latest(the instance-wide runners), notci, which serves the kirria org.