ftown-bridge 0.3.16 → 0.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,43 +0,0 @@
1
- ---
2
- name: bridge-harness
3
- description: Control local ftown-bridge sessions via auto-deployed ~/.ftown/bin/ftown-harness. Triggers on bridge harness, /bridge-harness, bridge sessions.
4
- ---
5
-
6
- # bridge-harness
7
-
8
- ## Entry (auto-deployed)
9
-
10
- ```bash
11
- ~/.ftown/bin/ftown-harness <cmd>
12
- ```
13
-
14
- Read `~/.ftown/harness-agent.md` on each bridge start. Never curl/lsof the local bridge API.
15
-
16
- ## Playbook
17
-
18
- ```bash
19
- ftown-harness status
20
- ftown-harness here -n 25 # tails log even if process dead (status=error)
21
- ftown-harness ls --tail 3 # log=N on each row; previews dead sessions with logs
22
- ftown-harness grep ftown "error|FAIL" -C 2
23
- ```
24
-
25
- ## Commands
26
-
27
- | Cmd | Notes |
28
- |-----|-------|
29
- | `here -n N` | Workspace walk-up; **tails when dead** if log exists |
30
- | `ls --tail N` | Shows `log=lines`; preview any session with logs |
31
- | `tail` / `grep` | ANSI+OSC stripped; `grep -C 2` context |
32
- | `send` | `--dry-run` first; `-s` submit; only when user asks |
33
- | `--json` | `ftown-harness --json ls` etc. |
34
-
35
- Lookup: exact name → substring → id prefix.
36
-
37
- ## Dead vs error
38
-
39
- `status=error` + `alive=false` does **not** mean no logs. Use `here`/`tail` — they read persisted terminal logs.
40
-
41
- ## context-mode
42
-
43
- Use `ftown-harness` in Bash only. No curl/wget to 127.0.0.1.