deferred-capture

# Deferred Capture Contract ## When To Use - Building a new plugin deferred-capture wrapper - Validating an existing wrapper against the contract - Adding new source labels or template fields ## When NOT To Use - Capturing a deferred item at runtime (use the plugin wrapper directly, e.g. `scripts/deferred_capture.py`) - Creating GitHub issues manually Specification that all plugin deferred-capture wrappers implement. Not a runtime dependency -- a convention. ## CLI Interface Required arguments: - `--title` (str): Concise description. Becomes issue title after `[Deferred]` prefix - `--source` (str): Origin skill. One of: war-room, brainstorm, scope-guard, feature-review, review, regression, egregore - `--context` (str): Why raised and why deferred Optional arguments: - `--labels` (str): Comma-separated additional labels beyond `deferred` + source - `--session-id` (str): Session ID. Canonical source: `$CLAUDE_SESSION_ID` env var, fallback: UTC timestamp `YYYYMMDD-HHMMSS` - `--artifact-path` (str): Absolute path or `$HOME`-based path to source artifact - `--captured-by` (str): `explicit` (default) or `safety-net` - `--dry-run` (flag): Print JSON output without creating issue ## Issue Template Title: `[Deferred] <title>` Labels: `deferred` + `<source>` Body: ## Deferred Item **Source:** <source> (session <session-id>) **Captured:** <YYYY-MM-DD> **Branch:** <current git branch> **Captured by:** <explicit|safety-net> ### Contex...