Add the forge-groom dev plan #49

Merged

vnprc merged 1 commit from agent/forge-groom-plan into master

2026-09-09 23:47:02 +01:00

allod-agent commented

2026-09-09 21:48:40 +01:00

Member

Adds the dev plan for the weekly self-hosted forge groom: a timer on a dev VM runs pi against the self-hosted deepseek model with the forge-groom skill, closes only what a merged Closes proves settled, labels the rest, and emails the owner one short report through an msmtp relay.
Nothing changes for a running machine; this is a plan. Four slices follow it: the skill (memory, open now), forge pr list -s (tools), the archetypes timer and mail module, and the private enablement with a scoped token and SMTP credential.
The decisions it records were taken with the owner today: dev-VM timer, deepseek thinking at medium, report plus label plus evidence-only closes, email not the forge, all repos weekly, one portable skill.
Residual risk is R3 because a scheduled process holds a forge token with issue-write scope; the plan bounds that with a token that cannot push or merge, a wrapper that never exports a credential into the model's environment, and a rollback of one revert plus one token revocation.
What proves each slice is named in its row: a by-hand run reproducing today's manual pass, fixture tests for the list flag, generated-unit inspection with a stub relay, and two real weekly emails read against the trackers before any autonomy widens.
If the plan is wrong, edit it; nothing executes until slice 4 lands.

Refs allod/strategy#48

Risk

R0 for this PR. The R3 above is the plan's residual risk for the work it schedules.

Validation

Sections follow allod/memory dev-plans.md and the template: tracking issue, goal, scope, risk with per-slice table, contracts, gates, acceptance tests, rollback.
Length is under the 150-line soft cap.
The forge capability the close rule depends on (pr list -s closed) was verified missing today (forge pr list -s is refused), and master's fast-forward-only history was verified to carry no PR bodies, which is why that slice exists.

Adds the dev plan for the weekly self-hosted forge groom: a timer on a dev VM runs `pi` against the self-hosted deepseek model with the `forge-groom` skill, closes only what a merged `Closes` proves settled, labels the rest, and emails the owner one short report through an msmtp relay. Nothing changes for a running machine; this is a plan. Four slices follow it: the skill (memory, open now), `forge pr list -s` (tools), the archetypes timer and mail module, and the private enablement with a scoped token and SMTP credential. The decisions it records were taken with the owner today: dev-VM timer, deepseek thinking at medium, report plus label plus evidence-only closes, email not the forge, all repos weekly, one portable skill. Residual risk is R3 because a scheduled process holds a forge token with issue-write scope; the plan bounds that with a token that cannot push or merge, a wrapper that never exports a credential into the model's environment, and a rollback of one revert plus one token revocation. What proves each slice is named in its row: a by-hand run reproducing today's manual pass, fixture tests for the list flag, generated-unit inspection with a stub relay, and two real weekly emails read against the trackers before any autonomy widens. If the plan is wrong, edit it; nothing executes until slice 4 lands. Refs allod/strategy#48 ## Risk R0 for this PR. The R3 above is the plan's residual risk for the work it schedules. ## Validation - Sections follow `allod/memory` `dev-plans.md` and the template: tracking issue, goal, scope, risk with per-slice table, contracts, gates, acceptance tests, rollback. - Length is under the 150-line soft cap. - The `forge` capability the close rule depends on (`pr list -s closed`) was verified missing today (`forge pr list -s` is refused), and master's fast-forward-only history was verified to carry no PR bodies, which is why that slice exists.

allod-agent added 1 commit

2026-09-09 21:48:40 +01:00

Add the forge-groom dev plan c01ee79953

Weekly self-hosted tracker triage: a dev-VM timer runs pi against the
self-hosted deepseek model with the forge-groom skill, closes only what
a merged Closes proves settled, labels the rest, and emails one short
report through an msmtp relay. Four slices: skill, forge pr list -s,
archetypes timer and mail module, private enablement.

Refs allod/strategy#48