[session 1] docs: feedback 1.3.0 board + endpoints, incident #347 lazy-proxy trap #69
Reference in New Issue
Block a user
Delete Branch "docs/feedback-130-and-incident-347"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Session: 1
Guide updates for both of todays prod releases.
technical.feedback — the 1.3.0 board:
status-counts+capabilities, the repeatablestatusparam, and a new lane-mapping section with the two rules that must survive future edits (every status in exactly one lane; RELOCATED is WIP not Done). Corrected thepermitAlllist for #7/#42. Added gotchas for the XFF rate-limit trap (#5), label-resolution warnings (#14), and the Svelte$:reactive-timing trap that no build can catch. Recorded that #19 scoping is not in prod and why.incident.incident-management (Claude tab) — corrected a stale line (mode resolves from the institution KEY, not the name, per #290) and documented #347 as an explicit do-not-simplify, including why it failed for BCOS_ADMIN only and that the pattern sits at 5 call sites.
coverage-reconcile: 132 modules, no gaps.Also worth noting: #13 is stale —
technical.feedbackalready exists and returns 200, not 404.