coilysiren/website
1
0
Fork 0
Code Issues 6 Pull requests Projects Releases Packages Wiki Activity Actions

Bring website devtools and CI into the current ward/dev-base world #69

New issue
Closed
opened 2026-07-09 16:29:41 +00:00 by coilyco-ops · 2 comments
coilyco-ops commented 2026-07-09 16:29:41 +00:00
Collaborator
Copy link

Problem

The website repo is split across several generations of repo tooling. The current live state shows:

  • .ward/ward.yaml exists and AGENTS.md points agents at ward.
  • .coily/coily.yaml still exists as a duplicate command surface.
  • README.md still tells agents to use .coily/coily.yaml and coily exec.
  • .pre-commit-config.yaml is pinned to the managed agentic-os block at v0.16.0, including retired closes-issue and conventional-commit hooks.
  • .github/workflows/config.yml and .github/workflows/trufflehog.yml still hold the CI and secret-scan automation.
  • .forgejo/workflows/ is absent, so canonical Forgejo does not have the current CI surface.

This overlaps older work in website#68, website#64, and website#57, but the repo needs one coherent pass instead of another narrow patch.

Do

  • Make ward the only documented dev command surface. Update README.md and any relevant docs from coily exec / .coily/coily.yaml to ward exec / .ward/ward.yaml.
  • Remove .coily/coily.yaml if the current repo conventions allow it. If a compatibility reason keeps it, document that reason in the issue comment before landing.
  • Update .pre-commit-config.yaml to the current agentic-os managed hook suite from Forgejo, removing retired commit-msg hooks. Prefer the agentic-os migration helper if present and applicable.
  • Add Forgejo workflow files for the normal website CI and offline secret scanning. Port the useful parts of the current GitHub config.yml and trufflehog.yml; do not port GitHub automerge.
  • Use the current AOS dev-base image conventions for Forgejo Actions. Keep package-manager behavior aligned with the repo's packageManager field and ward verbs.
  • Treat .github/workflows/pulse-refresh.yml as a separate design decision unless it clearly has a Forgejo equivalent. Document the decision in docs/ci-workflows.md.
  • Update docs/ci-workflows.md and docs/FEATURES.md if the workflow surface materially changes.
  • Comment on or close website#68, website#64, and website#57 as appropriate once this lands.

Acceptance

  • ward exec test-quick passes.
  • The agent runs any additional ward validation that the changed workflow or pre-commit surface makes relevant.
  • A fresh commit no longer tries to run retired closes-issue or conventional-commit hooks.
  • Forgejo has first-class CI and secret scanning for the canonical repo.
  • README and docs no longer instruct agents to use the retired coily surface.
## Problem The website repo is split across several generations of repo tooling. The current live state shows: * `.ward/ward.yaml` exists and AGENTS.md points agents at ward. * `.coily/coily.yaml` still exists as a duplicate command surface. * README.md still tells agents to use `.coily/coily.yaml` and `coily exec`. * `.pre-commit-config.yaml` is pinned to the managed agentic-os block at `v0.16.0`, including retired `closes-issue` and `conventional-commit` hooks. * `.github/workflows/config.yml` and `.github/workflows/trufflehog.yml` still hold the CI and secret-scan automation. * `.forgejo/workflows/` is absent, so canonical Forgejo does not have the current CI surface. This overlaps older work in website#68, website#64, and website#57, but the repo needs one coherent pass instead of another narrow patch. ## Do * Make ward the only documented dev command surface. Update README.md and any relevant docs from `coily exec` / `.coily/coily.yaml` to `ward exec` / `.ward/ward.yaml`. * Remove `.coily/coily.yaml` if the current repo conventions allow it. If a compatibility reason keeps it, document that reason in the issue comment before landing. * Update `.pre-commit-config.yaml` to the current agentic-os managed hook suite from Forgejo, removing retired commit-msg hooks. Prefer the agentic-os migration helper if present and applicable. * Add Forgejo workflow files for the normal website CI and offline secret scanning. Port the useful parts of the current GitHub `config.yml` and `trufflehog.yml`; do not port GitHub automerge. * Use the current AOS dev-base image conventions for Forgejo Actions. Keep package-manager behavior aligned with the repo's `packageManager` field and ward verbs. * Treat `.github/workflows/pulse-refresh.yml` as a separate design decision unless it clearly has a Forgejo equivalent. Document the decision in `docs/ci-workflows.md`. * Update `docs/ci-workflows.md` and `docs/FEATURES.md` if the workflow surface materially changes. * Comment on or close website#68, website#64, and website#57 as appropriate once this lands. ## Acceptance * `ward exec test-quick` passes. * The agent runs any additional ward validation that the changed workflow or pre-commit surface makes relevant. * A fresh commit no longer tries to run retired `closes-issue` or `conventional-commit` hooks. * Forgejo has first-class CI and secret scanning for the canonical repo. * README and docs no longer instruct agents to use the retired `coily` surface.
coilyco-ops commented 2026-07-09 16:29:51 +00:00
Author
Collaborator
Copy link

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-codex-website-69 on host kais-macbook-pro-2.local.

Reserved by ward agent --harness codex (reserved 2026-07-09T16:29:49Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (1h TTL). --force overrides.

Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).

run seed context — what this run is carrying (ward#609)
  • Resolved: coilysiren/website#69 · branch issue-69 · harness codex · workflow direct-to-main
  • Run: engineer-codex-website-69 · ward v0.493.0 · dispatched 2026-07-09T16:29:49Z
  • Comment thread: 0 included in the pre-flight read, 0 stripped (ward's own automated comments).

Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.493.0).

— Codex, via ward agent

<!-- ward-agent-reservation --> WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-website-69` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-09T16:29:49Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (1h TTL). `--force` overrides. **Do not comment on or edit this issue to steer the run while it is reserved.** The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a **new issue, dispatched fresh**. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494). <details><summary>run seed context — what this run is carrying (ward#609)</summary> - **Resolved:** `coilysiren/website#69` · branch `issue-69` · harness `codex` · workflow `direct-to-main` - **Run:** `engineer-codex-website-69` · ward `v0.493.0` · dispatched `2026-07-09T16:29:49Z` - **Comment thread:** 0 included in the pre-flight read, 0 stripped (ward's own automated comments). Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.493.0). </details> </details> <!-- ward-agent-signature --> — Codex, via `ward agent`
coilyco-ops commented 2026-07-09 16:50:08 +00:00
Author
Collaborator
Copy link

WARD-OUTCOME: done ✅

details

workflow: direct-to-main; review summary: review gate skipped by --skip-review / --no-review-gate

Landed the ward-only docs, removed .coily/coily.yaml, added Forgejo CI and offline secret scanning, and updated the managed pre-commit block. Closed #68, #64, and #57.

It felt iterative because Forgejo exposed one CI install failure that needed a second pass.

confidence: high

surprise: dev-base needed corepack and the test job was safest with direct pnpm install.

follow-ups: none.

WARD-OUTCOME: done ✅ <details><summary>details</summary> workflow: direct-to-main; review summary: review gate skipped by --skip-review / --no-review-gate Landed the ward-only docs, removed `.coily/coily.yaml`, added Forgejo CI and offline secret scanning, and updated the managed pre-commit block. Closed #68, #64, and #57. It felt iterative because Forgejo exposed one CI install failure that needed a second pass. confidence: high surprise: dev-base needed corepack and the test job was safest with direct `pnpm install`. follow-ups: none. </details>
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
burndown-2026-06
Backlog burndown June 2026

  
consult
A human decision, design, or external action must happen first. Fail-closed default for unlabeled/low-confidence.

  
headless
Agent can take it from open issue to merged change with no human in the loop. The auto-burndown queue.

  
icebox
Closed in the 2026-05-29 backlog burn-down; reopen if it becomes real

  
interactive
Agent does the work but pauses at a human checkpoint mid-flight (design choice, destructive step, human-only verification).

  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
P4

No labels
burndown-2026-06
consult
headless
icebox
interactive
P0
P1
P2
P3
P4
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilysiren/website#69
No description provided.