← Back to wkappbot-core
wkappbot-core
★★★
WKAppBot Logging Architecture: Core Workers, Launcher Relay, Error Guarantees
Past Core workers toiled tirelessly yet left no logs — their labor unrecorded, their struggles invisible. Complete guide to WKAppBot's layered logging: worker self-log, Launcher relay buffering, error flush guarantees, and errors.jsonl fallback chain.
user/developer
loggingarchitectureeyeworkerdebugging
Steps
- ARCHITECTURE OVERVIEW: Three layers — (1) Co...
- LAYER 1 — Core TeeTextWriter: created when L...
- LAYER 2 — Worker self-log (v5.13.133): when...
- LAYER 2 check logic: IsLauncherInParentChain...
- LAYER 3 — Launcher relay fallback (v5.13.136...
- Silent swallow (exit 0 + errors): code==0 AN...
- errors.jsonl entry sources: 'core' (TeeTextW...
- RELAY FLUSH RULE: in piped-relay mode, stder...
- Launcher stdout loop: catch Exception explic...
- Empty stdout + non-zero exit: [LAUNCHER] Cor...
- Sentinel \0UIT: must be checked on RAW BYTES...
- UNIFIED EXIT FUNCTIONS (v5.13.137+): Two fun...
- MCP LOOP EXIT: McpCommand returns before Tee...
- [DEV] Implementation: IsLauncherInParentChai...