agentwire-dev 1.44.0__tar.gz → 1.45.0__tar.gz

agentwire_dev-1.45.0/.agents/skills/wiki/SKILL.md

@@ -0,0 +1,105 @@
+---
+name: wiki
+description: "Manage the agentwire LLM Wiki knowledge base. Authoring is in-context; mechanical ops (query, lint, status, new, done) run through the deterministic `agentwire wiki` CLI / `wiki_*` MCP tools. Use when recording knowledge, querying it, or health-checking the wiki. Subcommands: /wiki ingest, /wiki query <question>, /wiki lint (incl. ground-truth audit against the codebase)"
+---
+
+# AgentWire Wiki
+
+LLM-maintained knowledge base at `~/.agentwire/wiki/`. Read `~/.agentwire/wiki/AGENTS.md` for the full schema and conventions.
+
+**How the loop actually works:** authoring is **in-context** — the session that learns something writes the page itself (`Write`/`Edit` into `wiki/<category>/<name>.md`), with full context, for free. That's the working path; there is **no scheduled batch ingester**. The *mechanical* parts — searching, health-checking, scaffolding, archiving sources — are deterministic and run through the `agentwire wiki` CLI (and the `wiki_query` / `wiki_lint` / `wiki_status` MCP tools), exactly like `/handoff` splits "LLM distills in-context, CLI renders deterministically."
+
+| Mechanical op | Command |
+|---|---|
+| Search the wiki | `agentwire wiki query <q> [--limit N] [--json]` / MCP `wiki_query` |
+| Health-check (structural + ground-truth) | `agentwire wiki lint [--strict] [--json]` / MCP `wiki_lint` |
+| Overview (counts, unprocessed raw, health) | `agentwire wiki status [--json]` / MCP `wiki_status` |
+| Scaffold a page with correct frontmatter | `agentwire wiki new <category> <name> [--title T]` |
+| Archive a consumed source | `agentwire wiki done <rawfile>` |
+
+(All stdlib-only — they run from a source checkout with no rebuild.)
+
+## Subcommands
+
+### `/wiki ingest`
+
+**Authoring is in-context and primary.** When you discover something worth keeping, write or update the page *now*, in your own session — `agentwire wiki new <category> <name>` scaffolds the frontmatter, then you fill in the body and add `[[page-name]]` wikilinks. This is how the wiki is maintained; don't wait for a batch job (there isn't one).
+
+`raw/` is an **optional verbatim-source inbox** — a place to stash an article, gist, transcript, or findings dump you might author from later. It is **not** the primary path and nothing drains it automatically.
+
+**To author from a stranded raw source:**
+1. Read the file in `raw/`.
+2. Identify entities (technologies, patterns, APIs, research topics) and, for each, create (`agentwire wiki new …`) or update the matching `wiki/<category>/<name>.md` — in-context, citing the raw file as a source.
+3. Add `[[page-name]]` wikilinks for cross-references.
+4. When the source is consumed, archive it: **`agentwire wiki done <rawfile>`** moves `raw/<f>` → `raw/processed/<f>` (content is never edited — only relocated, so immutability holds; "unprocessed = files directly in `raw/`" stays a trivial check, no `.ingested` marker).
+
+**Never edit the *content* of files in `raw/`** — they are immutable source material. `wiki done` only relocates them.
+
+### `/wiki query <question>`
+
+Answer a question grounded in wiki content.
+
+**Steps:**
+1. **`agentwire wiki query "<question>"`** (or MCP `wiki_query`) — deterministic ranked search (name/title weighted over body), returns top pages with `path + score + snippet`.
+2. Read the top pages it points at.
+3. Synthesize an answer citing specific wiki pages. (The CLI does **not** call an LLM — *you* synthesize, in your own context.)
+4. If the wiki doesn't have enough information, say so clearly — do not hallucinate.
+5. If you discover new knowledge while answering, write/update the relevant wiki pages (in-context).
+
+### `/wiki lint`
+
+Health check the wiki. Two passes: a **structural** pass (links, freshness, frontmatter) and a **ground-truth audit** that verifies concrete claims against the actual codebase. Both run from one command:
+
+```bash
+agentwire wiki lint            # structural + ground-truth, report-only
+agentwire wiki lint --json     # machine-readable findings
+agentwire wiki lint --strict   # exit 1 when issues found (CI)
+```
+
+**Structural pass (implemented as code in `agentwire/wiki.py`):**
+- **Stale pages**: `last_updated` older than 90 days
+- **Orphaned pages**: no other page links to them via `[[wikilink]]`
+- **Broken wikilinks**: `[[page-name]]` pointing to a non-existent page
+- **Missing/invalid frontmatter**: no frontmatter, missing `name`/`last_updated`, or an unparseable date
+
+It does NOT auto-fix — review and decide.
+
+#### Ground-truth audit
+
+The wiki accrues concrete claims about the codebase — `agentwire` subcommands and flags, repo file paths, config keys, qualified Python symbols — that nothing ever verifies. Left unchecked they rot into confident-but-wrong, which is worse than no wiki. This audit extracts the checkable assertions from every page and flags the ones that no longer resolve against the source. **`agentwire wiki lint` folds this pass in automatically** alongside the structural checks; the standalone module below is the same engine, handy for pointing at a different wiki/codebase.
+
+**Run it** (from a checkout of the agentwire repo — stdlib only, no build/install needed):
+
+```bash
+agentwire wiki lint                            # structural + this ground-truth pass
+python -m agentwire.wiki_audit                 # ground-truth pass only, against this repo
+python -m agentwire.wiki_audit --json          # machine-readable findings
+python -m agentwire.wiki_audit --strict        # exit 1 when drift is found (CI)
+python -m agentwire.wiki_audit \
+  --wiki-dir <dir> --repo-dir <repo>           # point at a different wiki / codebase
+```
+
+Each finding is reported as `wiki_file:line  [kind] claim  → reason`, so you can jump straight to the stale line.
+
+**What it checks (precision over recall — it would rather miss a stale claim than cry wolf on a true one):**
+
+| Kind | Claim it verifies | How |
+|------|-------------------|-----|
+| `subcommand` | `` `agentwire <cmd>` `` in a code span | `<cmd>` must be a registered `add_parser("<cmd>")` |
+| `flag` | `--flag` inside an `agentwire …` command span | must be a declared `add_argument("--flag")` |
+| `path` | repo-relative paths under `agentwire/ docs/ scripts/ tests/ examples/ .Codex/ .github/` | must exist on disk |
+| `symbol` | `` `module.symbol` `` where `agentwire/<module>.py` exists | `symbol` must be defined in that module |
+| `config-key` | dotted key near a config-file mention | every segment must be a field on a `@dataclass` in `config.py` |
+
+Scoping that keeps it quiet: flags/subcommands are only read inside code spans (bare prose mentioning `agentwire` or a flag isn't a claim); paths under the wiki's own `wiki/`/`raw/` trees and `~`/absolute paths are ignored; common method calls (`config.get`), filenames (`__main__.py`), and version strings (`agentwire v1.35.1`) are not mistaken for claims.
+
+**Act on it:** treat each finding as "a human renamed/removed/moved something and the wiki didn't follow." Confirm against the code, then update the wiki page (or, if the page is a deliberate historical record — e.g. a retrospective on removed code — leave it and note that in the page). As with the structural pass, the audit **never auto-fixes**.
+
+## Guidelines
+
+- Always read `~/.agentwire/wiki/AGENTS.md` first for the current schema
+- One page per entity — check before creating duplicates
+- Practical over theoretical — "how we use it" and "what broke" over textbook definitions
+- Include code snippets, commands, config examples
+- Date your updates in frontmatter `last_updated`
+- Cite sources (URLs, commit hashes, issue numbers)

agentwire_dev-1.45.0/.claude/skills/wiki/SKILL.md

@@ -0,0 +1,105 @@
+---
+name: wiki
+description: "Manage the agentwire LLM Wiki knowledge base. Authoring is in-context; mechanical ops (query, lint, status, new, done) run through the deterministic `agentwire wiki` CLI / `wiki_*` MCP tools. Use when recording knowledge, querying it, or health-checking the wiki. Subcommands: /wiki ingest, /wiki query <question>, /wiki lint (incl. ground-truth audit against the codebase)"
+---
+
+# AgentWire Wiki
+
+LLM-maintained knowledge base at `~/.agentwire/wiki/`. Read `~/.agentwire/wiki/CLAUDE.md` for the full schema and conventions.
+
+**How the loop actually works:** authoring is **in-context** — the session that learns something writes the page itself (`Write`/`Edit` into `wiki/<category>/<name>.md`), with full context, for free. That's the working path; there is **no scheduled batch ingester**. The *mechanical* parts — searching, health-checking, scaffolding, archiving sources — are deterministic and run through the `agentwire wiki` CLI (and the `wiki_query` / `wiki_lint` / `wiki_status` MCP tools), exactly like `/handoff` splits "LLM distills in-context, CLI renders deterministically."
+
+| Mechanical op | Command |
+|---|---|
+| Search the wiki | `agentwire wiki query <q> [--limit N] [--json]` / MCP `wiki_query` |
+| Health-check (structural + ground-truth) | `agentwire wiki lint [--strict] [--json]` / MCP `wiki_lint` |
+| Overview (counts, unprocessed raw, health) | `agentwire wiki status [--json]` / MCP `wiki_status` |
+| Scaffold a page with correct frontmatter | `agentwire wiki new <category> <name> [--title T]` |
+| Archive a consumed source | `agentwire wiki done <rawfile>` |
+
+(All stdlib-only — they run from a source checkout with no rebuild.)
+
+## Subcommands
+
+### `/wiki ingest`
+
+**Authoring is in-context and primary.** When you discover something worth keeping, write or update the page *now*, in your own session — `agentwire wiki new <category> <name>` scaffolds the frontmatter, then you fill in the body and add `[[page-name]]` wikilinks. This is how the wiki is maintained; don't wait for a batch job (there isn't one).
+
+`raw/` is an **optional verbatim-source inbox** — a place to stash an article, gist, transcript, or findings dump you might author from later. It is **not** the primary path and nothing drains it automatically.
+
+**To author from a stranded raw source:**
+1. Read the file in `raw/`.
+2. Identify entities (technologies, patterns, APIs, research topics) and, for each, create (`agentwire wiki new …`) or update the matching `wiki/<category>/<name>.md` — in-context, citing the raw file as a source.
+3. Add `[[page-name]]` wikilinks for cross-references.
+4. When the source is consumed, archive it: **`agentwire wiki done <rawfile>`** moves `raw/<f>` → `raw/processed/<f>` (content is never edited — only relocated, so immutability holds; "unprocessed = files directly in `raw/`" stays a trivial check, no `.ingested` marker).
+
+**Never edit the *content* of files in `raw/`** — they are immutable source material. `wiki done` only relocates them.
+
+### `/wiki query <question>`
+
+Answer a question grounded in wiki content.
+
+**Steps:**
+1. **`agentwire wiki query "<question>"`** (or MCP `wiki_query`) — deterministic ranked search (name/title weighted over body), returns top pages with `path + score + snippet`.
+2. Read the top pages it points at.
+3. Synthesize an answer citing specific wiki pages. (The CLI does **not** call an LLM — *you* synthesize, in your own context.)
+4. If the wiki doesn't have enough information, say so clearly — do not hallucinate.
+5. If you discover new knowledge while answering, write/update the relevant wiki pages (in-context).
+
+### `/wiki lint`
+
+Health check the wiki. Two passes: a **structural** pass (links, freshness, frontmatter) and a **ground-truth audit** that verifies concrete claims against the actual codebase. Both run from one command:
+
+```bash
+agentwire wiki lint            # structural + ground-truth, report-only
+agentwire wiki lint --json     # machine-readable findings
+agentwire wiki lint --strict   # exit 1 when issues found (CI)
+```
+
+**Structural pass (implemented as code in `agentwire/wiki.py`):**
+- **Stale pages**: `last_updated` older than 90 days
+- **Orphaned pages**: no other page links to them via `[[wikilink]]`
+- **Broken wikilinks**: `[[page-name]]` pointing to a non-existent page
+- **Missing/invalid frontmatter**: no frontmatter, missing `name`/`last_updated`, or an unparseable date
+
+It does NOT auto-fix — review and decide.
+
+#### Ground-truth audit
+
+The wiki accrues concrete claims about the codebase — `agentwire` subcommands and flags, repo file paths, config keys, qualified Python symbols — that nothing ever verifies. Left unchecked they rot into confident-but-wrong, which is worse than no wiki. This audit extracts the checkable assertions from every page and flags the ones that no longer resolve against the source. **`agentwire wiki lint` folds this pass in automatically** alongside the structural checks; the standalone module below is the same engine, handy for pointing at a different wiki/codebase.
+
+**Run it** (from a checkout of the agentwire repo — stdlib only, no build/install needed):
+
+```bash
+agentwire wiki lint                            # structural + this ground-truth pass
+python -m agentwire.wiki_audit                 # ground-truth pass only, against this repo
+python -m agentwire.wiki_audit --json          # machine-readable findings
+python -m agentwire.wiki_audit --strict        # exit 1 when drift is found (CI)
+python -m agentwire.wiki_audit \
+  --wiki-dir <dir> --repo-dir <repo>           # point at a different wiki / codebase
+```
+
+Each finding is reported as `wiki_file:line  [kind] claim  → reason`, so you can jump straight to the stale line.
+
+**What it checks (precision over recall — it would rather miss a stale claim than cry wolf on a true one):**
+
+| Kind | Claim it verifies | How |
+|------|-------------------|-----|
+| `subcommand` | `` `agentwire <cmd>` `` in a code span | `<cmd>` must be a registered `add_parser("<cmd>")` |
+| `flag` | `--flag` inside an `agentwire …` command span | must be a declared `add_argument("--flag")` |
+| `path` | repo-relative paths under `agentwire/ docs/ scripts/ tests/ examples/ .claude/ .github/` | must exist on disk |
+| `symbol` | `` `module.symbol` `` where `agentwire/<module>.py` exists | `symbol` must be defined in that module |
+| `config-key` | dotted key near a config-file mention | every segment must be a field on a `@dataclass` in `config.py` |
+
+Scoping that keeps it quiet: flags/subcommands are only read inside code spans (bare prose mentioning `agentwire` or a flag isn't a claim); paths under the wiki's own `wiki/`/`raw/` trees and `~`/absolute paths are ignored; common method calls (`config.get`), filenames (`__main__.py`), and version strings (`agentwire v1.35.1`) are not mistaken for claims.
+
+**Act on it:** treat each finding as "a human renamed/removed/moved something and the wiki didn't follow." Confirm against the code, then update the wiki page (or, if the page is a deliberate historical record — e.g. a retrospective on removed code — leave it and note that in the page). As with the structural pass, the audit **never auto-fixes**.
+
+## Guidelines
+
+- Always read `~/.agentwire/wiki/CLAUDE.md` first for the current schema
+- One page per entity — check before creating duplicates
+- Practical over theoretical — "how we use it" and "what broke" over textbook definitions
+- Include code snippets, commands, config examples
+- Date your updates in frontmatter `last_updated`
+- Cite sources (URLs, commit hashes, issue numbers)

agentwire_dev-1.45.0/.github/workflows/security.yml

@@ -0,0 +1,74 @@
+# Security CI for the damage-control matcher.
+#
+# Three independent signals:
+#   1. bypass-corpus  — the load-bearing gate. Asserts the known evasion vectors
+#                       (quoting/escaping, $VAR, substitution, tilde/$HOME secret
+#                       reads, non-rm deletion) stay BLOCK/ASK and a corpus of
+#                       safe everyday commands keeps PASSing. Merges gate on this.
+#   2. bandit         — advisory (non-blocking) static scan. There are intentional
+#                       `shell=True` sites (scheduler gates, service healthchecks),
+#                       so this informs review rather than blocking it.
+#   3. pip-audit      — known-vuln scan over the resolved dependency set, on PRs
+#                       and a weekly cron.
+name: security
+
+on:
+  push:
+    branches: [main]
+  pull_request:
+  schedule:
+    - cron: "0 7 * * 1"  # Mondays 07:00 UTC
+
+jobs:
+  bypass-corpus:
+    name: damage-control bypass corpus (merge gate)
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+        with:
+          python-version: "3.12"
+      - name: Sync dependencies
+        run: uv sync --extra dev
+      - name: Hooks are in sync with _core.py
+        run: uv run --no-sync python scripts/regen_damage_control_hooks.py --check
+      - name: Run bypass + sync + control-plane corpus
+        run: >
+          uv run --no-sync pytest -q
+          tests/unit/test_damage_control_bypass.py
+          tests/unit/test_damage_control_sync.py
+          tests/unit/test_control_plane_protection.py
+
+  bandit:
+    name: bandit (advisory)
+    runs-on: ubuntu-latest
+    continue-on-error: true  # intentional shell=True sites — advisory only
+    steps:
+      - uses: actions/checkout@v4
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+        with:
+          python-version: "3.12"
+      - name: Run bandit
+        run: uvx bandit -r agentwire -ll
+
+  pip-audit:
+    name: pip-audit (advisory)
+    runs-on: ubuntu-latest
+    # Advisory, not a merge gate: most flagged CVEs live in heavy OPTIONAL deps
+    # (torch/onnxruntime pulled by kokoro/moonshine) and are transitive, so
+    # hard-blocking every PR on them is noise. Keep it running on PRs + the
+    # weekly cron for visibility; the damage-control bypass corpus is the hard
+    # merge gate. Direct portal-facing deps are bumped explicitly in pyproject.
+    continue-on-error: true
+    steps:
+      - uses: actions/checkout@v4
+      - name: Install uv
+        uses: astral-sh/setup-uv@v5
+        with:
+          python-version: "3.12"
+      - name: Export locked dependencies
+        run: uv export --no-emit-project --format requirements-txt -o requirements.txt
+      - name: Audit dependencies
+        run: uvx pip-audit -r requirements.txt

{agentwire_dev-1.44.0 → agentwire_dev-1.45.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: agentwire-dev
-Version: 1.44.0
+Version: 1.45.0
 Summary: Multi-session voice web interface for AI coding agents
 Project-URL: Homepage, https://agentwire.dev
 Project-URL: Repository, https://github.com/dotdevdotdev/agentwire-dev
@@ -685,7 +685,7 @@ Classifier: Programming Language :: Python :: 3.13
 Classifier: Topic :: Software Development :: User Interfaces
 Requires-Python: >=3.10
 Requires-Dist: aiohttp-jinja2>=1.6
-Requires-Dist: aiohttp>=3.9.0
+Requires-Dist: aiohttp>=3.13.4
 Requires-Dist: av>=12.0.0
 Requires-Dist: jinja2>=3.1.0
 Requires-Dist: kokoro-onnx>=0.4.9; python_version < '3.14'
@@ -734,7 +734,6 @@ Description-Content-Type: text/markdown
   <a href="https://github.com/dotdevdotdev/agentwire-dev/stargazers"><img src="https://img.shields.io/github/stars/dotdevdotdev/agentwire-dev?style=flat&logo=github&color=00d4ff" alt="GitHub Stars"></a>
   <a href="https://pypi.org/project/agentwire-dev/"><img src="https://img.shields.io/pypi/pyversions/agentwire-dev" alt="Python"></a>
   <a href="https://github.com/dotdevdotdev/agentwire-dev/blob/main/LICENSE"><img src="https://img.shields.io/github/license/dotdevdotdev/agentwire-dev" alt="License"></a>
-  <a href="https://discord.gg/bspFZNTdUr"><img src="https://img.shields.io/badge/discord-join-5865F2?logo=discord&logoColor=white" alt="Discord"></a>
 </p>
 
 ---
@@ -774,7 +773,6 @@ pip install agentwire-dev
 
 # Setup (interactive)
 agentwire init
-agentwire generate-certs
 
 # Run
 agentwire portal start
@@ -785,7 +783,22 @@ agentwire portal start
 
 **Honest setup time:** under a minute to a working voice portal with a genuinely good voice — Kokoro-82M runs on CPU out of the box (one-time ~200 MB model download in the background; the browser voice covers the wait). ~15 minutes for the full experience: cloned voices via a self-hosted TTS shim, Whisper-grade transcription, phone-from-anywhere (certs + token).
 
-> **Network & trust model.** The portal binds `127.0.0.1` by default — local only. To use it from your phone, set `server.host: 0.0.0.0` in `~/.agentwire/config.yaml`. Non-loopback binds require an auth token (auto-generated on first start; print it with `agentwire portal token`) — your phone prompts for it once, then remembers it. Origin checks reject cross-site browser requests on every bind. Still: keep it on a trusted LAN. Never port-forward it or run it on a public-facing VPS — for internet access use Cloudflare Tunnel + Zero Trust. Details in [SECURITY.md](SECURITY.md).
+### Phone / LAN Access
+
+The portal binds to loopback (`127.0.0.1`) by default. To access the portal from your phone, tablet, or other devices on your local network:
+
+1. **Generate SSL certificates** (required for microphone access over non-loopback connections):
+   ```bash
+   agentwire generate-certs
+   ```
+2. **Enable LAN access**: set `server.host: 0.0.0.0` in `~/.agentwire/config.yaml`.
+3. **Get your auth token**: non-loopback connections require a bearer token. Print it with:
+   ```bash
+   agentwire portal token
+   ```
+4. **Connect**: Open `https://<your-machine-ip>:8765` on your phone and enter the token when prompted.
+
+Origin checks reject cross-site browser requests on every bind. Keep the portal on a trusted LAN — never port-forward it or run it on a public-facing VPS. For internet access, use Cloudflare Tunnel + Zero Trust. See [SECURITY.md](SECURITY.md) for details.
 
 <details>
 <summary><strong>Platform-specific instructions</strong></summary>
@@ -1002,7 +1015,6 @@ Quick links:
 
 ## Community
 
-- [Discord](https://discord.gg/bspFZNTdUr) - Chat, support, feature requests
 - [Issues](https://github.com/dotdevdotdev/agentwire-dev/issues) - Bug reports
 - [Website](https://agentwire.dev) - Docs and demos
 

{agentwire_dev-1.44.0 → agentwire_dev-1.45.0}/README.md

@@ -12,7 +12,6 @@
   <a href="https://github.com/dotdevdotdev/agentwire-dev/stargazers"><img src="https://img.shields.io/github/stars/dotdevdotdev/agentwire-dev?style=flat&logo=github&color=00d4ff" alt="GitHub Stars"></a>
   <a href="https://pypi.org/project/agentwire-dev/"><img src="https://img.shields.io/pypi/pyversions/agentwire-dev" alt="Python"></a>
   <a href="https://github.com/dotdevdotdev/agentwire-dev/blob/main/LICENSE"><img src="https://img.shields.io/github/license/dotdevdotdev/agentwire-dev" alt="License"></a>
-  <a href="https://discord.gg/bspFZNTdUr"><img src="https://img.shields.io/badge/discord-join-5865F2?logo=discord&logoColor=white" alt="Discord"></a>
 </p>
 
 ---
@@ -52,7 +51,6 @@ pip install agentwire-dev
 
 # Setup (interactive)
 agentwire init
-agentwire generate-certs
 
 # Run
 agentwire portal start
@@ -63,7 +61,22 @@ agentwire portal start
 
 **Honest setup time:** under a minute to a working voice portal with a genuinely good voice — Kokoro-82M runs on CPU out of the box (one-time ~200 MB model download in the background; the browser voice covers the wait). ~15 minutes for the full experience: cloned voices via a self-hosted TTS shim, Whisper-grade transcription, phone-from-anywhere (certs + token).
 
-> **Network & trust model.** The portal binds `127.0.0.1` by default — local only. To use it from your phone, set `server.host: 0.0.0.0` in `~/.agentwire/config.yaml`. Non-loopback binds require an auth token (auto-generated on first start; print it with `agentwire portal token`) — your phone prompts for it once, then remembers it. Origin checks reject cross-site browser requests on every bind. Still: keep it on a trusted LAN. Never port-forward it or run it on a public-facing VPS — for internet access use Cloudflare Tunnel + Zero Trust. Details in [SECURITY.md](SECURITY.md).
+### Phone / LAN Access
+
+The portal binds to loopback (`127.0.0.1`) by default. To access the portal from your phone, tablet, or other devices on your local network:
+
+1. **Generate SSL certificates** (required for microphone access over non-loopback connections):
+   ```bash
+   agentwire generate-certs
+   ```
+2. **Enable LAN access**: set `server.host: 0.0.0.0` in `~/.agentwire/config.yaml`.
+3. **Get your auth token**: non-loopback connections require a bearer token. Print it with:
+   ```bash
+   agentwire portal token
+   ```
+4. **Connect**: Open `https://<your-machine-ip>:8765` on your phone and enter the token when prompted.
+
+Origin checks reject cross-site browser requests on every bind. Keep the portal on a trusted LAN — never port-forward it or run it on a public-facing VPS. For internet access, use Cloudflare Tunnel + Zero Trust. See [SECURITY.md](SECURITY.md) for details.
 
 <details>
 <summary><strong>Platform-specific instructions</strong></summary>
@@ -280,7 +293,6 @@ Quick links:
 
 ## Community
 
-- [Discord](https://discord.gg/bspFZNTdUr) - Chat, support, feature requests
 - [Issues](https://github.com/dotdevdotdev/agentwire-dev/issues) - Bug reports
 - [Website](https://agentwire.dev) - Docs and demos
 

{agentwire_dev-1.44.0 → agentwire_dev-1.45.0}/SECURITY.md

@@ -39,11 +39,25 @@ This security policy applies to:
 
 AgentWire includes built-in security features:
 
-- **Damage Control Hooks:** Block 300+ dangerous command patterns
-- **Path Protection:** Prevent access to sensitive files (.env, SSH keys, credentials)
+- **Damage Control Hooks:** Block 300+ dangerous command patterns. Commands are
+  matched after shell-aware normalization (quote/escape stripping, simple `$VAR`
+  resolution); constructs that can't be statically verified (command
+  substitution, `eval`, `base64 -d | sh`) fail closed.
+- **Path Protection:** Prevent access to sensitive files (`.env`, SSH keys,
+  credentials) across shell, file edits/writes, **and native content reads**
+  (Read/Grep/Glob). Committed env templates (`.env.example`, `.sample`,
+  `.template`, `.dist`) are treated as secret-free and remain readable.
 - **Audit Logging:** All blocked operations are logged
 
-See `docs/wiki/internals/damage-control.md` for details.
+See `docs/wiki/internals/damage-control.md` for details, and
+`docs/wiki/security/damage-control-hardening.md` for the 2026-06 matcher
+hardening (control-plane path coverage, tilde/`$HOME` canonicalization, `.env`
+whole-component matching, shell-aware fail-closed matching, read-surface
+policing) and the new fail-closed-when-unattended behavior.
+
+### Redundant Permissions Bypass (`--dangerously-skip-permissions`)
+
+By default, AgentWire initializes Claude Code with the `--dangerously-skip-permissions` flag. This is safe because AgentWire implements its own **Damage Control Hooks** at the system shell level (installed via `agentwire hooks install`). Rather than relying on fragile, prompt-based AI dialogs for command approval, AgentWire intercepts and enforces safety rules directly in the shell. Bypassing Claude's built-in prompts prevents unnecessary interruptions and speeds up agent execution while keeping AgentWire's compensating shell-level controls in force.
 
 ## Trust Model
 

{agentwire_dev-1.44.0 → agentwire_dev-1.45.0}/SPONSORS.md

@@ -35,11 +35,11 @@ AgentWire is made possible by these generous supporters.
 
 | Tier | Amount | What you get |
 |---|---|---|
-| **Supporter** | $5/mo | Name in SPONSORS.md · Supporter role in Discord |
+| **Supporter** | $5/mo | Name in SPONSORS.md |
 | **Backer** | $15/mo | Everything in Supporter · Priority responses on your GitHub issues · Input on what gets built next |
 | **Pro** | $35/mo | Everything in Backer · Early access to new features · Vote on roadmap priorities · Beta branch access |
 | **Team** | $100/mo | Everything in Pro · Logo in README · Monthly 30-minute support call · Priority bug fixes |
-| **Enterprise** | $500/mo | Everything in Team · Dedicated Discord channel · 48-hour bug response · Quarterly roadmap review · Featured logo placement |
+| **Enterprise** | $500/mo | Everything in Team · 48-hour bug response · Quarterly roadmap review · Featured logo placement |
 
 ### One-Time
 

{agentwire_dev-1.44.0 → agentwire_dev-1.45.0}/agentwire/__init__.py

@@ -1,3 +1,3 @@
 """AgentWire - Multi-session voice web interface for AI coding agents."""
 
-__version__ = "1.44.0"
+__version__ = "1.45.0"