@ikon85/agent-workflow-kit 0.43.0 → 0.44.0

package/docs/adr/0009-teardown-authority-is-stateless-repository-classification.md

@@ -1,101 +0,0 @@
-# Teardown authority is stateless repository classification
-
-Status: accepted (2026-07-27, #320) — supersedes
-[ADR-0007](./0007-session-teardown-requires-provenance-bound-ownership.md)
-
-ADR-0007 derived teardown authority from persisted lifecycle evidence:
-ownership-proof refs acquired in atomic git transactions, frozen
-landing-attempt journals, baseline digests, no-follow identity binding, and a
-post-merge reload of the canonical cleanup policy. Every piece was locally
-justified, and the aggregate failed in practice: fifteen teardown/cleanup
-issues in two weeks (#245–#319), ~5,600 lines of lifecycle code, two recovery
-flags for the machinery's own bookkeeping, a legacy receipt contract, and
-refusals that did not name their cause (#319: 68,856 paths, 7.4 MB, zero
-actionable lines). The protection was aimed at narrow races between assessment
-and deletion; the cost was that ordinary sessions could no longer finish.
-
-We decided that teardown authority comes from the repository's **current
-state**, read at the moment of action, and from nothing else:
-
-1. **Git's own classification is the file taxonomy.** A tracked modification
-   blocks teardown. An untracked, non-ignored file blocks with a bounded
-   report (count plus top directories — never an unbounded path dump). An
-   ignored file is Scratch: the repository declared it not-work, and it is
-   deletable. "Ignored" means git's standard exclude sources
-   (`--exclude-standard`: repository `.gitignore` files, `.git/info/exclude`,
-   the global excludes file) — whatever the repository's own tooling treats as
-   ignored is deletion authority here too.
-2. **One hardcoded exception: `.env*` (basename glob).** Ignored yet
-   potentially irreplaceable. Before removal each `.env*` regular file is
-   compared byte-wise with its counterpart at the same relative path in the
-   main checkout, both opened no-follow: identical → derived copy, deletable;
-   divergent, absent in the main checkout, or either side not a regular file →
-   block with the exact files named. The check is a present-state comparison,
-   not a receipt.
-3. **The platform PR record authorizes branch deletion.** Force-deletion
-   requires exactly one PR matching the full tuple — this repository as base
-   repo, head repository equal to the base repo (no fork heads), head ref
-   equal to the branch name, base ref equal to the configured protected
-   branch, state merged — whose head SHA equals the branch tip OID; the OID
-   is re-read immediately before deletion, and zero matches, multiple
-   matches, an open PR on the same head, or any drift retains the branch.
-   Ancestry-merged branches (against a freshly fetched configured protected
-   branch — stale ancestry stops rather than guesses) delete normally. A
-   branch with neither stays and is reported. Without platform access this
-   degrades to ancestry-only, reported honestly.
-4. **Idempotency by re-check, not journal.** An interrupted landing is resumed
-   by re-running it; every step verifies present state (PR exists? merged?
-   worktree present?) and skips or proceeds. There is no persisted attempt
-   state to validate, archive, or recover.
-5. **A direct `/wrapup` invocation is the teardown authorization.** It lands
-   and tears down the worktree it runs in — including worktrees created by
-   external tools under foreign names and paths. The kit never conditions
-   teardown on its own naming or location conventions; the four classification
-   rules above are the only protection.
-6. **Deletion policy has exactly one configuration surface: the ignore
-   mechanism.** The consumer profile keeps structural facts only (worktree
-   root, templates, protected branches, sweep opt-in). `scratchPatterns` and
-   `landingGeneratedArtifactPatterns` are removed without migration —
-   including the shipped consumer migration that seeded them; making a file
-   deletable means ignoring it (ADR-0008's offered seeding remains the
-   supported way; its consequence about deriving `scratchPatterns` from the
-   seeded rules is obsolete with this decision).
-
-## Considered options
-
-- **Keep ADR-0007's provenance machinery:** rejected on empirical grounds. The
-  races it closes (a foreign file occupying an assessed path between
-  assessment and deletion, a same-name branch created concurrently) are rare
-  and low-harm next to the observed failure mode: routine teardown becoming
-  impossible and each repair adding machinery. The branch race is additionally
-  closed cheaper by the tip-SHA/PR comparison.
-- **Shipping default scratch patterns:** rejected. A default allowlist of the
-  deletable restarts the pattern catalog and its seeding, sync, and dialect
-  problems; `.gitignore` already encodes the same fact with universal
-  tooling.
-- **Migrating existing profiles and receipts:** rejected. The green-slate cut
-  is deliberate (#320): old keys are ignored, journaled attempts are inert
-  files, and no code path reads either. Maintaining both models would preserve
-  the complexity this decision removes.
-- **Location heuristic for externally created worktrees (land, don't tear
-  down):** rejected by the user. `/wrapup` means tear down; splitting the
-  outcome by worktree origin reintroduces an ownership notion.
-
-## Consequences
-
-- A worktree whose only untracked content is ignored dependency or build
-  output is removable with zero configuration. #319's failure class cannot
-  occur.
-- Refusals are bounded and name their cause; the fix is always visible
-  (commit the tracked change, handle the named `.env*`, ignore or remove the
-  named untracked files).
-- The accepted residual risk is explicit: between assessment and deletion a
-  file could in principle be replaced; a valuable file a consumer keeps
-  gitignored outside `.env*` is deletable at teardown. We trade these narrow
-  windows for a lifecycle that ordinary sessions can actually complete.
-- Planning sessions stop being a special case: durable content lands through
-  wrapup's Content route as ordinary work, scratch dies with the worktree,
-  and worktree creation binds to implementation, not planning.
-- The lifecycle implementation shrinks from a transaction protocol to a
-  classification function plus plumbing; its tests shift from race
-  choreography to classification truth tables.

package/docs/adr/0010-model-roster-replaces-the-optimization-dial.md

@@ -1,87 +0,0 @@
-# A Model roster replaces the optimization dial
-
-Status: accepted (2026-07-27, Program #287, Welle 18 / #294) — supersedes the
-Routing-policy clause of
-[ADR-0006](./0006-routing-knowledge-access-and-policy-are-separate.md)
-
-ADR-0006 made "optimization goals and optional advanced overrides" inputs of
-the Routing policy, and setup asked the user to pick Balanced, Quality, or
-Cost. That dial cannot be made to work. The goal is always the right model for
-the job, and a cheap-but-weak model can cost more per completed task than a
-strong one — so a Cost dial does not express a preference the resolver can act
-on without knowing cost per *completed* task, which no benchmark owner
-publishes. Meanwhile the dial was never read: `readRoutingProfile` has zero
-callers and `resolveRoute` always returns `routing-infrastructure-missing`.
-
-We decided the user control is a **Model roster** — a positive list of
-model-and-effort pairs the user authorizes — plus three **Standard routes**
-that decide when no decisive evidence covers the resolved Routing intent.
-
-1. **The optimization dial is removed everywhere it appears, not only from the
-   Routing policy.** The Routing intent loses its optimization goal too. What a
-   user is willing to spend is a Routing profile choice, not a property of the
-   work; leaving the field in the intent while the resolver ignores it would
-   leave a dead concept in the domain language. The glossary entry and the
-   intent schema both drop it.
-2. **`unreachable` and `missingInfrastructure` are kept.** They are unrelated to
-   the dial, and the resolver's fallback semantics depend on them.
-3. **Transport authorization belongs to the Routing profile.** Selecting Claude
-   Code and Codex does not authorize either to drive the other's CLI. ADR-0006
-   is already explicit that a detected transport is not an approved one; this
-   ADR names where the approval is stored — the global profile document, as its
-   own interview answer, narrowable per project by intersection only.
-4. **The Routing policy is derived, not stored.** The profile is the stored
-   personal choice and carries no revision. The policy is the constraint object
-   derived from profile plus inventory for one dispatch, and it carries the
-   composed revision so a Dispatch receipt can prove which constraints applied.
-5. **Cost is displayed and used as a tiebreak inside a cohort of identical
-   currency and unit — never as the ranking motor.** This is what the Cost dial
-   was reaching for, at the only altitude where it is honest.
-6. **The Kit ships no opinion about which models are good.** Excluding a model
-   is one user's preference under one subscription, not a default truth. The
-   inventory stays unfiltered per ADR-0006; the roster authorizes.
-
-## `inherit` is retained, and the condition that would have removed it
-
-This ADR was drafted to remove `inherit` entirely if verify-spike 18c (#296)
-could not prove that the session-default model-and-effort pair is readable back
-and identifiable against the roster. **The spike came back positive, so
-`inherit` is retained** in the constrained form: inheritance is permitted only
-when the session-default pair is attested *and* inside the effective roster,
-and otherwise blocks.
-
-The condition under which `inherit` is removed entirely therefore stands as a
-standing test, not a settled negative: **if the session-default pair ceases to
-be readable back on a surface, `inherit` is removed for that surface rather
-than left as an unprovable path.** A receipt that cannot name the pair it
-inherited is not proof of anything.
-
-The spike qualifies the retention with an identification requirement. One and
-the same Claude Code session reports its default model under three different
-identifiers — `opus[1m]` in `~/.claude/settings.json`, `claude-opus-5[1m]` in
-the session's init event, and `claude-opus-5` in the server-returned
-`message.model`. The attested channel is the one that drops the context
-variant. Roster identification therefore requires an explicit normalization
-rule and a decision on whether the context variant is part of pair identity;
-until that rule exists, "identified against the roster" is not a check a
-receipt may claim to have made.
-
-## Consequences
-
-- ADR-0006's Routing-policy clause (item 3, "optimization goals and optional
-  advanced overrides") and its closing sentence "Model preferences and
-  optimization overrides remain optional advanced settings" no longer describe
-  the system. The rest of ADR-0006 — the separation of Evidence catalog, Access
-  graph, and Routing policy; detection is not authorization; the surface
-  adapter capability declaration; the Dispatch receipt requirement — stands
-  unchanged and remains the foundation this ADR builds on.
-- `advanced.optimization` is removed from the Routing profile schema, and
-  `optimization` from the Routing policy schema, each with a deterministic
-  version-aware decoder that records the drop rather than silently discarding a
-  choice the user made.
-- Setup's Balanced / Quality / Cost prompt is replaced by roster admission and
-  Standard-route nomination.
-- Model-and-effort is pair identity. Effort domains are per model — some models
-  support an effort level others do not, and some carry no effort axis at all —
-  so a pair is authorized as a pair, never as a model with an effort attached
-  afterwards.

package/docs/agents/board-sync.md

@@ -1,74 +0,0 @@
-<!-- setup-workflow: state=filled; mode=github-projects-v2 -->
-# Board sync — GitHub Projects field IDs
-
-The workflow board is [Agent Workflow Kit](https://github.com/users/iKon85/projects/3). Board-managed skills address it through the profile below and `scripts/board-sync.py`.
-
-<!-- board-sync:profile -->
-```json
-{
-  "repo": "iKon85/agent-workflow-kit",
-  "project": {
-    "number": 3,
-    "owner": "iKon85",
-    "nodeId": "PVT_kwHOAuH31M4BdM5V"
-  },
-  "fields": {
-    "status": {
-      "id": "PVTSSF_lAHOAuH31M4BdM5VzhXwFOk",
-      "options": {
-        "Idea": "357a9b54",
-        "Triaged": "463d3f21",
-        "Spec": "1cd0343b",
-        "In Progress": "35e6c509",
-        "Review": "51f16b28",
-        "Done": "491150b6"
-      },
-      "roles": {
-        "idea": "Idea",
-        "triaged": "Triaged",
-        "spec": "Spec",
-        "inProgress": "In Progress",
-        "review": "Review",
-        "done": "Done"
-      }
-    },
-    "wave": "PVTF_lAHOAuH31M4BdM5VzhXwFWg",
-    "cluster": "PVTF_lAHOAuH31M4BdM5VzhXwFWk",
-    "specPath": "PVTF_lAHOAuH31M4BdM5VzhXwFWo",
-    "planPath": "PVTF_lAHOAuH31M4BdM5VzhXwFWs",
-    "phase": {
-      "id": "PVTSSF_lAHOAuH31M4BdM5VzhXwFWw",
-      "options": {
-        "P1": "9c8c93e0",
-        "P2": "cf741bec",
-        "P3": "8a69a61e"
-      }
-    }
-  },
-  "labels": {
-    "readyForAgent": "ready-for-agent",
-    "typePrefix": "type:",
-    "clusterType": "type:cluster",
-    "waveStub": "wave-stub",
-    "programType": "type:program"
-  },
-  "branchPrefixes": ["feat", "fix", "chore", "docs"],
-  "prMarkers": {
-    "partOf": "Part of",
-    "retroMarker": "**Retro:**",
-    "retroValues": ["ran", "skipped"]
-  },
-  "headings": {
-    "vorBau": "Clarify Before Build"
-  },
-  "titles": {
-    "wavePrefix": "Welle"
-  },
-  "wrapup": {
-    "remoteBranchSweep": true
-  }
-}
-```
-
-The Program route uses phases `P1`, `P2`, and `P3`. Saved board views remain a GitHub UI concern; the machine profile above is the workflow SSOT.
-

package/docs/agents/code-review.md

@@ -1,14 +0,0 @@
-<!-- setup-workflow: state=filled -->
-# Code-review project layer
-
-## Standards sources in this repo
-
-- `CLAUDE.md` and `AGENTS.md`
-- `docs/conventions/`
-- The originating issue or PRD for the Spec axis
-
-## Adjacent review tooling
-
-- `spec-self-critique` reviews plans before code exists; it does not replace diff review.
-- Security audits and simplification passes remain narrower complementary checks.
-

package/docs/agents/workflow-capabilities.json

@@ -1,28 +0,0 @@
-{
-  "worktreeLifecycle": {
-    "enabled": true,
-    "worktreeRoot": ".worktrees",
-    "branchTemplate": "{type}/{issue}-{slug}",
-    "pathTemplate": "{issue}-{slug}",
-    "branchRegex": "^(?:feat|fix|chore|docs)/(?P<issue>\\d+)-",
-    "mainBranches": ["main"],
-    "protectedBranches": ["main"],
-    "scratchPatterns": [
-      "PLAN.md",
-      "PLAN-REVIEW-LOG.md",
-      ".claude/logs/**"
-    ],
-    "setupEntry": "python3 scripts/worktree-lifecycle/setup.py",
-    "setupSteps": [],
-    "riskyCommandPatterns": [
-      "\\b(?:npm|pnpm|yarn)\\s+(?:run\\s+)?(?:test|typecheck|build)\\b",
-      "\\bgit\\s+(?:commit|push)\\b"
-    ]
-  },
-  "wrapup": {
-    "landingGeneratedArtifactPatterns": [
-      "dist-kit/**",
-      "**/__pycache__/**"
-    ]
-  }
-}