@event4u/agent-config 10.4.0 → 12.0.0

package/dist/agent-src/commands/ghostwriter.md

@@ -2,7 +2,6 @@
 model_tier: inherit
 name: ghostwriter
 pack: gtm-marketing
-tier: 2
 visibility: internal
 description: Ghostwriter cluster — fetch, write, list, show, and delete public-figure voice profiles (the third voice primitive alongside personas/ and .agent-user.md).
 argument-hint: "[fetch|write|list|show|delete] [args]"

package/dist/agent-src/commands/grill-me.md

@@ -2,7 +2,6 @@
 model_tier: inherit
 name: grill-me
 pack: product-reasoning
-tier: 2
 visibility: internal
 description: Alias for /challenge-me — interactive grill-style interview that sharpens a fuzzy plan/idea into a copyable Markdown pitch
 argument-hint: "[vision|with-docs] [flags] [seed]"

package/dist/agent-src/commands/humanize.md

@@ -2,7 +2,6 @@
 model_tier: inherit
 name: humanize
 pack: gtm-marketing
-tier: 2
 visibility: internal
 description: Remove AI-writing tells from pasted text or a file — runs the humanizer skill's draft→audit→final loop and prints the rewrite plus a detector summary.
 argument-hint: "[path] [--voice=<slug|me>] [--language=en|de|auto]"

package/dist/agent-src/commands/image/analyse.md

@@ -2,7 +2,6 @@
 model_tier: high
 name: image-analyse
 pack: ai-video
-tier: 2
 visibility: internal
 cluster: image
 sub: analyse

package/dist/agent-src/commands/image/create.md

@@ -2,7 +2,6 @@
 model_tier: high
 name: image-create
 pack: ai-video
-tier: 2
 visibility: internal
 cluster: image
 sub: create

package/dist/agent-src/commands/image/verify.md

@@ -2,7 +2,6 @@
 model_tier: high
 name: image-verify
 pack: ai-video
-tier: 2
 visibility: internal
 cluster: image
 sub: verify

package/dist/agent-src/commands/image.md

@@ -2,7 +2,6 @@
 model_tier: inherit
 name: image
 pack: ai-video
-tier: 2
 visibility: internal
 cluster: image
 description: Character-image fidelity orchestrator — analyse, create, and verify a character image against its canon. Routes to analyse, create, verify.

package/dist/agent-src/commands/implement-ticket.md

@@ -5,7 +5,6 @@ pack: engineering-base
 intent: "Implement a tracker ticket end-to-end from its id"
 routes_to: [refine-ticket, feature-planning]
 replaces: []
-tier: 0
 visibility: visible
 skills: [refine-ticket, feature-planning]
 description: Drive a ticket end-to-end through refine → memory → analyze → plan → implement → test → verify → report — Option-A loop over the `work_engine` engine, block-on-ambiguity, no auto-git.

package/dist/agent-src/commands/jira-ticket.md

@@ -5,7 +5,6 @@ pack: product-basic
 intent: "Read a Jira ticket from the branch and implement the feature or fix the bug"
 routes_to: [jira-integration, feature-planning]
 replaces: []
-tier: 1
 visibility: advanced
 skills: [laravel]
 description: Read Jira ticket from branch name, analyze linked Sentry issues, implement feature or fix bug

package/dist/agent-src/commands/judge/on-diff.md

@@ -2,7 +2,6 @@
 model_tier: high
 name: judge-on-diff
 pack: engineering-base
-tier: 2
 visibility: internal
 cluster: judge
 sub: on-diff

package/dist/agent-src/commands/judge/solo.md

@@ -2,7 +2,6 @@
 model_tier: high
 name: judge-solo
 pack: engineering-base
-tier: 2
 visibility: internal
 cluster: judge
 sub: solo

package/dist/agent-src/commands/judge/steps.md

@@ -2,7 +2,6 @@
 model_tier: high
 name: judge-steps
 pack: engineering-base
-tier: 2
 visibility: internal
 cluster: judge
 sub: steps

package/dist/agent-src/commands/judge.md

@@ -7,7 +7,6 @@ pack: engineering-base
 intent: "Adversarial-judging dispatcher — solo, on-diff, steps"
 routes_to: [judge-solo, judge-on-diff, judge-steps]
 replaces: []
-tier: 1
 visibility: advanced
 description: Judge orchestrator — routes to solo, steps, on-diff
 cluster: judge

package/dist/agent-src/commands/knowledge/cross-repo.md

@@ -2,7 +2,6 @@
 model_tier: medium
 name: knowledge-cross-repo
 pack: product-discovery
-tier: 2
 visibility: internal
 cluster: knowledge
 sub: cross-repo

package/dist/agent-src/commands/knowledge/forget.md

@@ -2,7 +2,6 @@
 model_tier: medium
 name: knowledge-forget
 pack: product-discovery
-tier: 2
 visibility: internal
 cluster: knowledge
 sub: forget

package/dist/agent-src/commands/knowledge/ingest.md

@@ -2,7 +2,6 @@
 model_tier: medium
 name: knowledge-ingest
 pack: product-discovery
-tier: 2
 visibility: internal
 cluster: knowledge
 sub: ingest

package/dist/agent-src/commands/knowledge/list.md

@@ -2,7 +2,6 @@
 model_tier: medium
 name: knowledge-list
 pack: product-discovery
-tier: 2
 visibility: internal
 cluster: knowledge
 sub: list

package/dist/agent-src/commands/knowledge.md

@@ -2,7 +2,6 @@
 model_tier: medium
 name: knowledge
 pack: product-discovery
-tier: 2
 visibility: internal
 description: Knowledge orchestrator — routes to ingest, list, forget. Local-only file ingestion into the agent memory namespace.
 argument-hint: "[ingest|list|forget|cross-repo] [args]"

package/dist/agent-src/commands/memory/add.md

@@ -2,7 +2,6 @@
 model_tier: medium
 name: memory-add
 pack: memory
-tier: 2
 visibility: internal
 cluster: memory
 sub: add

package/dist/agent-src/commands/memory/learn-low-impact.md

@@ -2,7 +2,6 @@
 model_tier: medium
 name: memory-learn-low-impact
 pack: memory
-tier: 2
 visibility: internal
 cluster: memory
 sub: learn-low-impact

package/dist/agent-src/commands/memory/load.md

@@ -2,7 +2,6 @@
 model_tier: medium
 name: memory-load
 pack: memory
-tier: 2
 visibility: internal
 cluster: memory
 sub: load

package/dist/agent-src/commands/memory/mine-session.md

@@ -2,7 +2,6 @@
 model_tier: medium
 name: memory-mine-session
 pack: memory
-tier: 2
 visibility: internal
 cluster: memory
 sub: mine-session

package/dist/agent-src/commands/memory/promote.md

@@ -2,7 +2,6 @@
 model_tier: medium
 name: memory-promote
 pack: memory
-tier: 2
 visibility: internal
 cluster: memory
 sub: promote

package/dist/agent-src/commands/memory/propose.md

@@ -2,7 +2,6 @@
 model_tier: medium
 name: memory-propose
 pack: memory
-tier: 2
 visibility: internal
 cluster: memory
 sub: propose

package/dist/agent-src/commands/memory.md

@@ -7,7 +7,6 @@ pack: memory
 intent: "Manage the agent memory layer — add, load, promote, propose"
 routes_to: [memory-add, memory-load, memory-mine-session, memory-promote, memory-propose, memory-learn-low-impact]
 replaces: []
-tier: 1
 visibility: advanced
 description: Memory orchestrator — routes to add, load, mine-session, promote, propose
 cluster: memory

package/dist/agent-src/commands/mission/upgrade.md

@@ -5,7 +5,6 @@ pack: engineering-base
 intent: "Upgrade a Laravel application one major version (10→11, 11→12) via the gated /work engine with a structured breaking-change catalog"
 routes_to: [dependency-upgrade]
 replaces: []
-tier: 1
 visibility: advanced
 skills: [dependency-upgrade]
 framework: laravel

package/dist/agent-src/commands/mode.md

@@ -5,7 +5,6 @@ pack: meta
 intent: "Switch the active role-mode (developer/reviewer/tester/po/incident/planner)"
 routes_to: [role-mode-adherence]
 replaces: []
-tier: 1
 visibility: advanced
 description: Set the active role mode — prints the contract, lists default skills, and refuses work outside the contract (see role-contracts)
 argument-hint: "[developer|reviewer|tester|po|incident|planner|none]"

package/dist/agent-src/commands/module/create.md

@@ -2,7 +2,6 @@
 model_tier: medium
 name: module-create
 pack: engineering-base
-tier: 2
 visibility: internal
 cluster: module
 sub: create

package/dist/agent-src/commands/module/explore.md

@@ -2,7 +2,6 @@
 model_tier: medium
 name: module-explore
 pack: engineering-base
-tier: 2
 visibility: internal
 cluster: module
 sub: explore

package/dist/agent-src/commands/module.md

@@ -4,7 +4,6 @@ name: module
 disable-model-invocation: true
 argument-hint: "[create|explore] [args]"
 pack: engineering-base
-tier: 2
 visibility: internal
 description: Module orchestrator — routes to create, explore
 cluster: module

package/dist/agent-src/commands/optimize/agents-dir.md

@@ -2,7 +2,6 @@
 model_tier: medium
 name: optimize-agents-dir
 pack: meta
-tier: 2
 visibility: internal
 cluster: optimize
 sub: agents-dir

package/dist/agent-src/commands/optimize/augmentignore.md

@@ -3,7 +3,6 @@ model_tier: medium
 skills: [agent-docs-writing]
 name: optimize-augmentignore
 pack: meta
-tier: 2
 visibility: internal
 cluster: optimize
 sub: augmentignore

package/dist/agent-src/commands/optimize/deep.md

@@ -2,7 +2,6 @@
 model_tier: high
 name: optimize-deep
 pack: meta
-tier: 2
 visibility: internal
 sub: deep
 cluster: optimize

package/dist/agent-src/commands/optimize/project.md

@@ -2,7 +2,6 @@
 model_tier: high
 name: optimize-project
 pack: meta
-tier: 2
 visibility: internal
 sub: project
 cluster: optimize

package/dist/agent-src/commands/optimize/prompt.md

@@ -2,7 +2,6 @@
 model_tier: inherit
 name: optimize-prompt
 pack: meta
-tier: 2
 visibility: internal
 sub: prompt
 cluster: optimize

package/dist/agent-src/commands/optimize/rtk.md

@@ -2,7 +2,6 @@
 model_tier: medium
 name: optimize-rtk
 pack: meta
-tier: 2
 visibility: internal
 cluster: optimize
 sub: rtk

package/dist/agent-src/commands/optimize/skills.md

@@ -2,7 +2,6 @@
 model_tier: medium
 name: optimize-skills
 pack: meta
-tier: 2
 visibility: internal
 cluster: optimize
 sub: skills

package/dist/agent-src/commands/optimize.md

@@ -7,7 +7,6 @@ pack: meta
 intent: "Optimization dispatcher — skills, rtk, augmentignore, agents-dir, project sweep, prompt, deep autonomous loop"
 routes_to: [optimize-skills, optimize-rtk, optimize-augmentignore, optimize-agents-dir, optimize-project, optimize-prompt, optimize-deep]
 replaces: []
-tier: 1
 visibility: advanced
 description: Optimize orchestrator — routes to skills, agents-dir, augmentignore, rtk-filters, project (project-wide sweep), prompt (AI-prompt polish), deep (autonomous deep-refactoring loop)
 cluster: optimize

package/dist/agent-src/commands/orchestrate.md

@@ -2,7 +2,6 @@
 model_tier: medium
 name: orchestrate
 pack: meta
-tier: 2
 visibility: internal
 cluster: orchestrate
 skills: [subagent-orchestration]

package/dist/agent-src/commands/override/create.md

@@ -2,7 +2,6 @@
 model_tier: medium
 name: override-create
 pack: meta
-tier: 2
 visibility: internal
 cluster: override
 sub: create

package/dist/agent-src/commands/override/manage.md

@@ -2,7 +2,6 @@
 model_tier: medium
 name: override-manage
 pack: meta
-tier: 2
 visibility: internal
 cluster: override
 sub: manage

package/dist/agent-src/commands/override.md

@@ -4,7 +4,6 @@ name: override
 disable-model-invocation: true
 argument-hint: "[create|manage] [args]"
 pack: meta
-tier: 2
 visibility: internal
 description: Override orchestrator — routes to create, manage
 cluster: override

package/dist/agent-src/commands/package/reset.md

@@ -2,7 +2,6 @@
 model_tier: medium
 name: package-reset
 pack: meta
-tier: 2
 visibility: internal
 sub: reset
 cluster: package

package/dist/agent-src/commands/package/test.md

@@ -2,7 +2,6 @@
 model_tier: medium
 name: package-test
 pack: meta
-tier: 2
 visibility: internal
 sub: test
 cluster: package

package/dist/agent-src/commands/package.md

@@ -7,7 +7,6 @@ pack: meta
 intent: "Package dispatcher — test the package install or reset the installed state"
 routes_to: [package-test, package-reset]
 replaces: []
-tier: 2
 visibility: internal
 description: Package orchestrator — routes to test (verify the package install) and reset (restore installed state)
 cluster: package

package/dist/agent-src/commands/post-as/ghostwriter.md

@@ -2,7 +2,6 @@
 model_tier: inherit
 name: post-as-ghostwriter
 pack: gtm-marketing
-tier: 2
 visibility: internal
 cluster: post-as
 sub: ghostwriter

package/dist/agent-src/commands/post-as/me.md

@@ -2,7 +2,6 @@
 model_tier: inherit
 name: post-as-me
 pack: gtm-marketing
-tier: 2
 visibility: internal
 cluster: post-as
 sub: me

package/dist/agent-src/commands/post-as.md

@@ -2,7 +2,6 @@
 model_tier: inherit
 name: post-as
 pack: gtm-marketing
-tier: 2
 visibility: internal
 description: Consumer-facing write entry points — :me drafts in the maintainer's own voice from .agent-user.md (no disclosure); :ghostwriter is a thin alias for /ghostwriter:write (mandatory disclosure footer).
 argument-hint: "[me|ghostwriter] [args]"

package/dist/agent-src/commands/pr/create/description-only.md

@@ -3,7 +3,6 @@ model_tier: medium
 name: git-pr-create-description-only
 pack: git
 replaces: [create-pr-description-only, create-pr:description-only]
-tier: 2
 visibility: internal
 cluster: git-pr-create
 sub: description-only

package/dist/agent-src/commands/pr/create.md

@@ -7,7 +7,6 @@ pack: git
 intent: "Open a pull request with a generated description and stripped attribution footers"
 routes_to: [git-workflow]
 replaces: [create-pr]
-tier: 1
 visibility: advanced
 cluster: git-pr-create
 skills: [git-workflow]
@@ -68,52 +67,92 @@ gate.
 
 Run, in order:
 
-1. `git fetch origin {target-base} --quiet` (default: `main`).
-2. `git rev-list --count HEAD..origin/{target-base}` — number of
-   commits HEAD is **behind** the base.
-3. `gh pr list --state open --base {target-base} --limit 20 --json number,headRefName,files`
-   — open PRs targeting the same base.
+1. **Ask the gate, never hand-roll the comparison:**
+
+   ```bash
+   npx tsx node_modules/@event4u/agent-config/src/scripts/check_branch_freshness.ts
+   ```
+
+   It resolves the base itself — explicit `--base`, else the base of the **open
+   PR for this branch** as the forge reports it, else the repo default the server
+   reports for `HEAD`. Do **not** substitute
+   `git rev-list --count HEAD..origin/main`: that hardcodes a base this branch may
+   not target, and it reads the local tracking ref, which is a fetch from earlier
+   in the session — a memory, not a check (`direct-answers` Iron Law 2).
+
+   **Exit `0` is not a verdict — it means only "did not refuse".** `1` = behind.
+   `0` covers "current", "could not verify", and every path with nothing to
+   check: a no-op in CI, a detached HEAD, and standing on the base branch
+   itself. Read the line, not just the status. A run that could not reach the
+   base prints `NOT VERIFIED` and still exits `0`, deliberately, so an offline
+   push is never blocked by a network failure; treating that as a clean pass is
+   the one misread this gate cannot protect you from.
+
+   **And under `--quiet` a genuine pass prints nothing at all** — that is how
+   `taskfiles/ci-fast.yml` invokes it, so silence there is the success case, not
+   a missing verdict. Every path that has NOT verified stays loud even under
+   `--quiet`. Run it without the flag when you need to read a verdict.
+
+2. `gh pr list --state open --base {resolved-base} --limit 20 --json number,headRefName,files`
+   — open PRs targeting the same base, for the overlap question below.
 
 **Decision matrix:**
 
-| Behind | Overlapping open PR touches same files? | Action |
+| Gate | Overlapping open PR touches same files? | Action |
 |---|---|---|
-| `0` | — | Proceed to Step 2 |
-| `1–N` | No | **Merge `origin/main` in** — `git merge origin/{target-base} --no-edit` — then proceed. No need to ask; state that you did it. Abort + surface only on conflict. |
-| `1–N` | **Yes** | STOP — surface the overlapping PR number, ask: stack on top of it / wait for it to land / proceed-anyway-and-accept-conflicts / cancel |
-
-A branch behind its base is **not** current — bring `main` in **before** the PR
+| exit `0`, prints `branch is current` | — | Proceed to Step 2 |
+| exit `1` | No | **Merge the base in** — `git fetch origin && git merge origin/{resolved-base} --no-edit` — then run the regeneration set below, then proceed. No need to ask; state that you did it. |
+| exit `1` | **Yes** | STOP — surface the overlapping PR number, ask: stack on top of it / wait for it to land / proceed-anyway-and-accept-conflicts / cancel |
+| exit `0`, prints `NOT VERIFIED` | — | The base could not be reached, so freshness is **unknown** — not confirmed. Re-run once; if it persists, say the check did not run rather than reporting a pass. A base that `ls-remote` cannot resolve (deleted or renamed after the PR opened, or a fork base) lands here too. |
+| warns `could not ask the forge` | — | The **default** base was checked and an open PR against a different base was **not** ruled out. Say so; do not report it as a clean freshness pass. |
+| exit `0`, prints nothing, `--quiet` given | — | The success case for the preflight invocation. Any non-verifying path would have printed even under `--quiet`. |
+| exit `0`, says `standing on <base> itself` / `detached HEAD` / `no-op in CI` | — | Nothing to check — a branch cannot be behind itself, a detached HEAD has no branch, and in CI the forge owns mergeability. Not a freshness pass; do not cite it as one. |
+
+A branch behind its base is **not** current — bring the base in **before** the PR
 exists, never after. Auto-merge when there is no file overlap (the common case);
 only ask when an overlapping open PR makes the base genuinely ambiguous. Never
 improvise the base or silently proceed when behind **and** overlapping. The
 10-second fetch beats hours of rebase reconciliation after the parent PR lands.
 
-**On merge conflict: regenerate, don't abort.** Most conflicts on this class of
-branch are in **generated files** — the roadmap dashboard
-(`agents/roadmaps-progress.md`), `docs/proof.md`, the `dist/agent-src/`
-projection, tool projections. Those are resolved **by regenerating from the merged sources**,
-never by hand-picking hunks:
-
-1. `./agent-config roadmap:progress` → resolves the dashboard.
-2. `./scripts-run src/scripts/build_proof` → resolves `docs/proof.md`.
-3. `bash src/scripts/condense.sh --sync`, then `--check` → resolves any
-   conflict inside `dist/agent-src/` by re-projecting from the merged source.
+**After EVERY merge — not only on conflict — regenerate the derived files.**
+This is the half that gets skipped, because a merge that lands cleanly *looks*
+finished. It is not: these files are **generated**, so a clean auto-merge of
+them produces a file that describes neither side's sources. The dashboard is the
+usual casualty — it merges without a conflict marker and then reports a roadmap
+set that no longer exists.
+
+1. `./agent-config roadmap:progress` → the roadmap dashboard.
+2. `./scripts-run src/scripts/build_proof` → `docs/proof.md`.
+3. `bash src/scripts/condense.sh --sync`, then `--check` → re-projects
+   `dist/agent-src/` from the merged source.
 4. Stage the regenerated files, complete the merge, and re-run the touched
    verification before pushing.
 
-Only a conflict in **hand-authored** content (source code, prose you or the
-other PR wrote) is surfaced to the user; a generated-file conflict never is.
+On a **conflict**, the same four steps are the resolution — regenerate from the
+merged sources, never hand-pick hunks. Only a conflict in **hand-authored**
+content (source code, prose you or the other PR wrote) is surfaced to the user;
+a generated-file conflict never is.
 
 ### 1b-ii. Update freshness — MANDATORY on EVERY later push to an open PR
 
 The gate above is not creation-only. **Every subsequent push** to a branch with
 an open PR (a CI fix, a review response, a follow-up commit) re-runs the same
-sequence first: `git fetch origin {target-base}` → behind-check → merge
-`origin/{target-base}` in (regenerating on conflict as above) → verify → push.
+sequence first: `check_branch_freshness` → on exit `1`, merge
+`origin/{resolved-base}` in → regenerate the derived files → verify → push.
 A PR that sits open while its base advances goes stale silently; keeping the
 base merged **at every touch** means it stays `mergeStateStatus: CLEAN` instead
-of accumulating conflicts for the moment the user wants to merge. If the
-behind-check shows `0`, the step costs one fetch and nothing else.
+of accumulating conflicts for the moment the user wants to merge. If the gate
+exits `0`, the step costs one `ls-remote` and nothing else.
+
+Once the PR exists, this is also when the resolution gets *more* precise rather
+than less: the gate can now read the PR's real `baseRefName` from the forge, so
+a stacked or release-line PR is measured against the branch it will actually
+merge into instead of against the repo default.
+
+Where the project wires this gate into its pre-push chain, a push that goes out
+through the hook is covered without a separate step. Run it by hand when you push
+with the hook bypassed, or when you are about to open the PR some time after the
+last push — that gap is exactly where a base moves unseen.
 
 ### 1c. PR-gate — archive completed roadmaps (MANDATORY)
 

package/dist/agent-src/commands/prediction-pool.md

@@ -2,7 +2,6 @@
 model_tier: inherit
 name: prediction-pool
 pack: fun
-tier: 2
 visibility: internal
 description: "Fill a prediction pool (kicktipp, football/basketball WM): optimize expected points under the rules, enter tips via Playwright. Triggers 'Tippspiel', 'kicktipp', 'predict the pool'."
 argument-hint: "[event] [--pool-url <url>] [--council off|event|match] [--submit] [--fresh|--continue]"

package/dist/agent-src/commands/prepare-for-review.md

@@ -2,7 +2,6 @@
 model_tier: high
 name: prepare-for-review
 pack: engineering-base
-tier: 2
 visibility: internal
 skills: [git-workflow, quality-tools]
 description: Prepare a PR branch for local review — updates main and merges the full branch chain so the branch is up to date

package/dist/agent-src/commands/profile/activate.md

@@ -2,7 +2,6 @@
 model_tier: medium
 name: profile-activate
 pack: meta
-tier: 2
 visibility: internal
 cluster: profile
 sub: activate

package/dist/agent-src/commands/profile/deactivate.md

@@ -2,7 +2,6 @@
 model_tier: medium
 name: profile-deactivate
 pack: meta
-tier: 2
 visibility: internal
 cluster: profile
 sub: deactivate

package/dist/agent-src/commands/profile/show.md

@@ -2,7 +2,6 @@
 model_tier: medium
 name: profile-show
 pack: meta
-tier: 2
 visibility: internal
 cluster: profile
 sub: show

package/dist/agent-src/commands/profile.md

@@ -2,7 +2,6 @@
 model_tier: medium
 name: profile
 pack: meta
-tier: 2
 visibility: internal
 description: Session-profile orchestrator — activate / deactivate / show the active packs for this session (recommendation-bias surface filter, no persistence)
 argument-hint: "[activate|deactivate|show] [args]"

package/dist/agent-src/commands/project/analyze.md

@@ -2,7 +2,6 @@
 model_tier: high
 name: project-analyze
 pack: engineering-base
-tier: 2
 visibility: internal
 sub: analyze
 cluster: project