History

Gud Boi 7952eb0634 Distinguish websocket receive and relay timeouts The `proxy_msgs()` deadline covers both `ws.get_message()` and `snd.send()`. Repeated socket-ready reports with no first relay could therefore mean either a silent source or a blocked local consumer; the old generic reset log could not distinguish them. Track the currently awaited operation and report its phase, URL, deadline, accumulated timeout count and reset threshold on each timeout. Snapshot `NoBsWs._timeout` once per iteration so the log reflects the deadline that actually elapsed. Keep the existing shared deadline, counter behavior and reconnect policy intact. Add two real loopback regressions: a silent websocket server and one payload blocked on an unconsumed zero-capacity Trio relay. Require the matching timeout phase and URL before the reset budget is exhausted. The 15 selected Binance/websocket cases pass. The human observes this after invalid `.usdm.` startup followed by corrected `.usdtm.` input. Metadata accepts the typo but later history lookup expects canonical keys. Record that investigation as context; this diagnostic patch does not fix FQME validation, failed-startup cleanup or prove the cause of corrected-feed stalls. Prompt-IO: ai/prompt-io/opencode/20261028T180856Z_032580bf_timeout_phase.md (this patch was generated in some part by `opencode` using `gpt-6.1-sol` (`openai`))		2026-10-28 14:35:57 -04:00
..
claude-code	Add `ai/` integration docs w/ `/commit-msg` usage	2026-03-05 15:30:34 -05:00
prompt-io	Distinguish websocket receive and relay timeouts	2026-10-28 14:35:57 -04:00
README.md	Add `ai/` integration docs w/ `/commit-msg` usage	2026-03-05 15:30:34 -05:00
ib-recovery-candidate.md	Document bounded IB recovery and downstream replay	2026-10-23 11:36:29 -04:00

README.md

AI Tooling Integrations

Documentation and usage guides for AI-assisted development tools integrated with this repo.

Each subdirectory corresponds to a specific AI tool or frontend and contains usage docs for the custom skills/prompts/workflows configured for it.

Originally introduced in PR #69; track new integration ideas and proposals in issue #79.

Integrations

Tool	Directory	Status
Claude Code	`claude-code/`	active

Adding a New Integration

Create a subdirectory named after the tool (use lowercase + hyphens), then add:

A README.md covering setup, available skills/commands, and usage examples
Any tool-specific config or prompt files

ai/
├── README.md                  # <- you are here
├── claude-code/
│   └── README.md
├── opencode/                  # future
│   └── README.md
└── <your-tool>/
    └── README.md

Conventions

Skill/command names use hyphen-case (commit-msg, not commit_msg)
Each integration doc should describe what the skill does, how to invoke it, and any output artifacts it produces
Keep docs concise; link to the actual skill source files (under .claude/skills/, etc.) rather than duplicating content