Skip to content

docs: replace Jaeger screenshot TODO with section scaffold#102

Closed
constk wants to merge 7 commits into
developfrom
chore/85-beads-issue-queue
Closed

docs: replace Jaeger screenshot TODO with section scaffold#102
constk wants to merge 7 commits into
developfrom
chore/85-beads-issue-queue

Conversation

@constk
Copy link
Copy Markdown
Owner

@constk constk commented May 25, 2026

What & why

The observability section of README.md (lines 83–94 before this change) had a TODO block where the Jaeger trace screenshot should go. This PR promotes the placeholder to a real subsection — heading, caption, link to src/observability/spans.py — so the section reads cleanly today even while the screenshot is outstanding.

The PNG itself still needs to be captured. The original capture recipe is preserved inside an HTML comment, alongside the exact one-line markdown to paste when docs/images/jaeger-trace.png is committed. Hiding the placeholder inside an HTML comment rather than a broken-image reference keeps the rendered README clean in the meantime.

Note for the maintainer. Closing #92 fully needs one follow-up: run docker compose up, capture the trace, commit the PNG, and replace the HTML comment with the image reference (the comment includes the exact line to paste). One-line change once the PNG exists.

Closes #92.

Test plan

  • Visual diff only on README.md "Screenshots" section
  • Rendered README has no broken image references
  • Capture recipe + paste-ready markdown line preserved in HTML comment

Invariants affected

None — references the existing semconv-keys-only constraint (already enforced via src/observability/spans.py constants) but adds no new rule.

New deps / actions / external surface

None.

Linked issue

Closes #92

constk and others added 6 commits April 27, 2026 22:52
release: bring main up to develop (every harness ticket)
release: sync main with develop (Vite proxy fix + README screenshots)
release: bring main up to develop (Teller v1.4 → v1.10.3 backport)
release: bring main up to develop (Teller v1.12.0 backports + audit follow-up)
…t compile gate)

Applies the actionable items from the PR-86 review:

- docs/BEADS.md: lead with a one-sentence "what Beads is" + upstream link;
  state the stance explicitly (optional/additive, recommended for agent-driven
  flows, GitHub remains authoritative); add a YAML example block under
  Recommended Bead fields; replace the duplicated Closure checklist with a
  Bead-specific narrowing that cites the PR template + CONTRIBUTING; call out
  that .beads/ is wiped by git clean -fdx.
- .github/pull_request_template.md: collapse the "Local Beads" section into
  an HTML-commented opt-in block so it is invisible in the rendered preview
  until a Beads-using team uncomments it.
- CONTRIBUTING.md: document the one-shot git renormalisation step for
  Windows clones after the .gitattributes change lands.
- tests/test_scripts_compile.py: regression gate that py_compiles every
  .github/scripts/*.py. The "scripts unparseable" review finding was based on
  an older local Python — PEP 758 (3.14) makes the unparenthesised except
  clauses valid, so the scripts ARE fine on the project pin. The test
  guards against an actual syntax error landing in future.
@constk constk closed this May 25, 2026
@constk constk deleted the chore/85-beads-issue-queue branch May 25, 2026 14:16
constk added a commit that referenced this pull request May 26, 2026
pip-audit on develop is flagging two transitive-dep CVEs:

- idna 3.13            CVE-2026-45409   (fix in 3.15+)
- starlette 1.0.0      PYSEC-2026-161   (fix in 1.0.1+)

Both are surfaced via fastapi/httpx. Bumps via:

    uv lock --upgrade-package idna --upgrade-package starlette

Resolves to idna 3.16 (3.15 was the listed fix; 3.16 is a further
patch with the same fix) and starlette 1.1.0 (minor bump; FastAPI is
compatible with it). All 192 unit tests pass on the upgraded lock.

Bumps the project self-version 0.2.10 -> 0.2.11 per
docs/DEVELOPMENT.md.

Unblocks the pip-audit CI gate on #99, #100, #101, #102 (and any
other PRs currently sitting on develop), all of which inherit the
flagged transitive CVEs from develop and cannot pass that gate until
this lands.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants