issues: file #23 (skill v2); research: gl0w-swarm feedback

diff --git a/.forge/issues/4b137271-8ba4-46f2-b09b-7ab22133085f/issue.md b/.forge/issues/4b137271-8ba4-46f2-b09b-7ab22133085f/issue.mdnew file mode 100644index 0000000..4c3678c--- /dev/null+++ b/.forge/issues/4b137271-8ba4-46f2-b09b-7ab22133085f/issue.md@@ -0,0 +1,51 @@1+---2+id: 4b137271-8ba4-46f2-b09b-7ab22133085f3+title: 'skill v2: fold gl0w-swarm feedback — git bridge, ci execution, merge/never-delete clarity, spec pointer (within budget)'4+state: open5+labels: []6+assignees: []7+milestone: null8+created: 2026-09-08T07:00:43Z9+updated: null10+---11+SOURCE: gl0w-swarm dogfood feedback, first read of the contract.12+Verified against SKILL_TEXT today: 650B/15ln; cap 900B/30ln;13+golden test skill_single_source_body_equals_skill_text pins14+skill/skill.md body == SKILL_TEXT. Review verdict: philosophy15+lines all praised; gaps are procedural/git-bridge, exactly where a16+terse skill bleeds.17+18+ADD to the contract, priority order:19+1. git bridge (MUST, keep full form): .forge/ is committed and20+   travels with the repo; a PR is a git branch (from a worktree).21+2. ci execution (MUST): steps are scripts; f0rge ci RUNS them in22+   filename order; first nonzero exit = fail verdict (keep23+   pass|fail|running|cancelled lifecycle words).24+3. merge + never-delete clarity: f0rge merge applies and prints25+   conflicts, never resolves; merged PR folder STAYS (state:26+   merged); only the branch is deleted. never-delete holds for all27+   entities — the fix is clarity, NOT a carve-out.28+4. archive destination: archive moves the entity folder to29+   .forge/archive/ (the dangling "moves folder" verb gets a target).30+5. start: f0rge init creates the .forge/ skeleton; idempotent, safe31+   to run anytime (fold into the usage line if bytes demand).32+6. format pointer: spec/schema.md is the frozen format truth;33+   labels.md/milestones.md are the label/milestone registries.34+35+CUT (explicitly out of scope): full skeleton enumeration36+(discoverable in one ls; formats belong in spec/, not the37+contract); repo-specific conventions (AGENTS.md placement,38+gitignores, migration scope) — never bake per-repo facts into a39+generic contract.40+41+RULES: budget cap 900B/30ln UNCHANGED — no PLAN §M2 change, no42+budget-test change. If the draft exceeds 900B, compress by priority:43+items 1-2 keep full form; items 3-6 bend (drop exemplars, fold init44+into usage, tighten wording). Keep the opener "f0rge v1: CONTRACT45+(not help)" and the semantics of all existing lines (id/number/46+files/tree/frontmatter/never-delete/wiki/usage/json). Touch no other47+file: no -h, no root help, no spec, no core.48+49+DONE means: SKILL_TEXT and skill/skill.md body byte-identical;50+skill_within_budget + golden test pass; full cargo test --workspace51+green; f0rge ci run verdict pass on the branch.

diff --git a/.forge/wiki/research/gl0w-swarm-feedback.md b/.forge/wiki/research/gl0w-swarm-feedback.mdnew file mode 100644index 0000000..5093b0d--- /dev/null+++ b/.forge/wiki/research/gl0w-swarm-feedback.md@@ -0,0 +1,43 @@1+# gl0w-swarm feedback on the f0rge skill (first external read)2+3+Date: 2026-09-08. Source: the gl0w project's swarm (different,4+larger models) reading `f0rge --skill` cold, during migration.5+Tracked in issue #23.6+7+## What worked (verbatim signal)8+tree, frontmatter, never delete, --jq / "never parse prose" — used9+immediately. Philosophy lines are sound.10+11+## Gaps found (procedural / git-bridge layer, not philosophy)12+1. (retracted by user — user mistype, not a skill fault) binary13+   name "forge" vs "f0rge".14+2. Nothing says the forge needs creating: `f0rge init`.15+3. Tree line omits ci.env, releases/, merges/, labels.md,16+   milestones.md — formats unknown without ls + spec/.17+4. THE big one: the contract never says .forge/ is committed and18+   travels in git; PRs-as-branches, worktrees, branch scrub all19+   invisible.20+5. Merge semantics invisible: who resolves conflicts; "scrubbed"21+   vs "never delete" tension.22+6. CI execution model fuzzy: does `f0rge ci` run steps or record23+   them? (It runs them; orchestrator was also fuzzy — real hole.)24+7. "archive moves folder" — to WHERE? .forge/archive/ never named.25+8. labels.md/milestones.md formats opaque.26+27+## Orchestrator triage (adopted 1:1 in #23)28+Keep: git bridge (MUST), ci execution (MUST), merge+never-delete29+clarity (no carve-out — merged PR folder STAYS state:merged, only30+the branch dies), archive destination, init bootstrap, spec/31+format pointer. Cut: full skeleton enumeration (discoverable), all32+repo-specific conventions (gitignores, AGENTS.md placement,33+migration scope).34+35+## Budget decision36+Cap stays 900B/30ln — smallest comprehensive skill, start as we37+mean to go on. Compress by priority if drafting exceeds it.38+39+## Also learned40+- `f0rge issue create --body` accepts multi-line bodies41+  (quoted-scalar fix holds).42+- The .forge formatters: releases/out + ci/runs are gitignored by43+  repo policy — NOT a contract fact.\ No newline at end of file