← 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
logging architecture eye worker debugging

## Steps

1. ARCHITECTURE OVERVIEW: Three layers — (1) Co...
2. LAYER 1 — Core TeeTextWriter: created when L...
3. LAYER 2 — Worker self-log (v5.13.133): when...
4. LAYER 2 check logic: IsLauncherInParentChain...
5. LAYER 3 — Launcher relay fallback (v5.13.136...
6. Silent swallow (exit 0 + errors): code==0 AN...
7. errors.jsonl entry sources: 'core' (TeeTextW...
8. RELAY FLUSH RULE: in piped-relay mode, stder...
9. Launcher stdout loop: catch Exception explic...
10. Empty stdout + non-zero exit: [LAUNCHER] Cor...
11. Sentinel \0UIT: must be checked on RAW BYTES...
12. UNIFIED EXIT FUNCTIONS (v5.13.137+): Two fun...
13. MCP LOOP EXIT: McpCommand returns before Tee...
14. [DEV] Implementation: IsLauncherInParentChai...

🔒 Pro Skill
Get Pro Access →