---
description: Add a self-triaging issue to the svamp backlog
allowed-tools: Bash(svamp issue add:*), Bash(svamp issue:*)
---
Add the following to this session's issue backlog. Run:

```
svamp issue add "$ARGUMENTS" --verify-cmd "<a command that FAILS now and passes once fixed>"
```

**Attach a verify.** `svamp issue close` RUNS the verify-cmd — that is what makes a close a
gate rather than a rubber stamp. An issue filed without one closes UNGATED, and
`scripts/check-issue-verify-cmds.mjs` cannot see it either (#1586: 64 issues filed in one night
with `verify: null`, 62 closed by nothing). Pick whichever form fits:

- `--verify-cmd "<shell command>"` — the default. It must exit NON-ZERO on the current tree.
- `--verify "<criterion>"` — when no shell command can express it (a perceptual or on-device
  result). An agent judges it at close time.
- `--manual` — when only a human can confirm it.

Everything else is defaulted, not inferred: with no `--label` the issue has none, and it is
created untriaged and `inline`. Run `svamp issue guide triage` if you want it labelled,
scoped, or routed to crew.

Then reply with one line: the new issue id and title. Do not do the work yet — this
just captures it. (To work the backlog autonomously, set a goal:
`/goal work this session's issue backlog until `svamp issue pending` is empty — run it
each turn and paste the output`.)