teknium1
704f0b1c91
`terminal(background=true, notify_on_complete=true)` appended its watcher descriptor to `process_registry.pending_watchers`, which only the post-turn hooks drain. A process that finished while the turn that launched it was still running (an agent sleep-polling for hours) had no watcher task at all: the completion_queue entry sat inert, nothing was injected, and the chat stayed mute until that turn ended (#112033). - `_register_completion_watcher` arms the watcher on the live gateway loop at registration (`GatewayRunner.arm_process_watcher`, via the existing `_gateway_runner_ref` / `_gateway_loop` seam that send_message and cron already use); `pending_watchers` stays the fallback while the gateway is not serving (checkpoint recovery at startup, shutdown). - The agent-notify branch of `_run_process_watcher` keeps its design (the agent's next turn is the user-facing report) but, when the launching turn is still active at process exit, the injection only queues a follow-up — so the concise receipt is sent to the chat right away instead of never. The busy check is taken before injection because the injected turn itself installs the adapter's session guard. Live probe (real process, real GatewayRunner loop, fake telegram adapter, busy session): before — pending_watchers=1 after exit, 0 watcher tasks, 0 injections, 0 receipts; after — pending_watchers=0, watcher task armed at launch, 1 injection, 1 concise receipt. Control (idle session): 1 injection, 0 receipts, unchanged. Slimmer redo of #112038 by @KoNit-K: same two gaps closed, without a second scheduler registry / loop attribute on ProcessRegistry and GatewayRunner. Co-authored-by: KoNit-K <124019182+KoNit-K@users.noreply.github.com>
Website
This website is built using Docusaurus, a modern static website generator.
Installation
yarn
Local Development
yarn start
This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.
Build
yarn build
This command generates static content into the build directory and can be served using any static contents hosting service.
Deployment
Using SSH:
USE_SSH=true yarn deploy
Not using SSH:
GIT_USER=<Your GitHub username> yarn deploy
If you are using GitHub pages for hosting, this command is a convenient way to build the website and push to the gh-pages branch.
Diagram Linting
CI runs ascii-guard to lint docs for ASCII box diagrams. Use Mermaid (````mermaid`) or plain lists/tables instead of ASCII boxes to avoid CI failures.