plano/docs
Syed Hashmi 041ba75034
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
2026-04-24 13:36:51 -07:00
..
source signals: restore the pre-port flag marker emoji 2026-04-24 13:36:51 -07:00
build_docs.sh fix build break (#730) 2026-02-09 10:08:20 -08:00
CNAME Update docs to Plano (#639) 2025-12-23 17:14:50 -08:00
Dockerfile fix build break (#730) 2026-02-09 10:08:20 -08:00
Makefile Docs branch - v1 of our tech docs (#69) 2024-09-20 17:08:42 -07:00
README.md add readme and docker build (#81) 2024-09-25 10:05:59 -07:00
requirements.txt Doc Update (#129) 2024-10-06 16:54:34 -07:00
routing-api.md Model affinity for consistent model selection in agentic loops (#827) 2026-04-08 17:32:02 -07:00

Generate HTML from reStructuredText files

To generate docs execute following command,

sh build_docs.sh

Requirements

This build system requires docker to be intsalled and running locally.