Brummel
3e96e74457
New label for observable misbehaviour distinct from additive-feature work and clean-up tasks. The /boss pickup order treats a bug differently from a feature (a bug typically gets RED-first TDD via skills/debug, a feature goes through brainstorm), so the label earns its keep. Tagged in Gitea (6 of 24 issues): - #7 io/print_float always-emit-.0 (surface vs runtime printer inconsistent) - #9 ailang-plan-recon site-undercount (tool under-counted 4× across two milestones) - #10 design_schema_drift.rs fidelity widening (test produces false negatives on §"Data model" gaps) - #12 Zero-arg `(app f)` rejected at parse (parser disagrees with the AST schema) - #15 *.bump_s throughput baseline stale (bench false-positive on environmental drift) - #16 check.py RC-latency *.max_us (bench false-positive: 3-of-3 null changes) Borderline cases left unlabelled (diagnostic usability, load_workspace limitation, dormant constraint-drop, advisory Sweep-5 wart) — they aren't observable wrong behaviour, just suboptimal. In-tree changes: - CLAUDE.md: Gitea-issues bullet adds `bug` to the label set with the same description string Gitea carries. - skills/boss/SKILL.md: Step 1 filter snippet includes `bug`. - skills/brainstorm/SKILL.md: Step 7.5 tea-create template --labels choice set includes `bug`. Distribution after tagging: 3 feature + 6 bug + 5 idea + 10 unlabelled = 24 open issues. Verification: cargo test --workspace 647/0/2, architect_sweeps exit 0.