Syed A. Hashmi dafd245332 signals: restore the pre-port flag marker emoji (🚩) (#913) ... * signals: restore the pre-port flag marker emoji #903 inadvertently replaced the legacy FLAG_MARKER (U+1F6A9, '🚩') with '[!]', which broke any downstream dashboard / alert that searches span names for the flag emoji. Restores the original marker and updates the #910 docs pass to match. - crates/brightstaff/src/signals/analyzer.rs: FLAG_MARKER back to "\\u{1F6A9}" with a comment noting the backwards-compatibility reason so it doesn't drift again. - docs/source/concepts/signals.rst and docs/source/guides/observability/ tracing.rst: swap every '[!]' reference (subheading text, example span name, tip box, dashboard query hint) back to 🚩. Verified: cargo test -p brightstaff --lib (162 passed, 1 ignored); sphinx-build clean on both files; rendered HTML shows 🚩 in all flag-marker references. Made-with: Cursor * fix: silence manual_checked_ops clippy lint (rustc 1.95) Pre-existing warning in router/stress_tests.rs that becomes an error under CI's -D warnings with rustc 1.95. Replace the manual if/else with growth.checked_div(num_iterations).unwrap_or(0) as clippy suggests. Made-with: Cursor		2026-04-24 13:54:53 -07:00
..
src	signals: restore the pre-port flag marker emoji (🚩) (#913)	2026-04-24 13:54:53 -07:00
Cargo.toml	add jemalloc and /debug/memstats endpoint for OOM diagnosis (#885)	2026-04-23 13:59:12 -07:00