Upstream source
Evaluate and port Kpa-clawbot/CoreScope#2068: show the running CoreScope version in the navigation drawer using the existing /api/health response.
Intended behaviour
- Render
CoreScope <version> in the drawer footer.
- Link it to this fork's releases page, not the upstream repository.
- Put commit and build time in the tooltip when available.
- Fetch
/api/health only when the drawer is opened and only after its viewport/availability gate.
- Cache the request for the page lifetime so reopening the drawer adds no requests.
- A failed, non-OK or version-less health response leaves a neutral
CoreScope label rather than blank or undefined text.
- Write all remote values with
textContent; do not inject health fields as HTML.
Fork-specific checks
- Confirm the current
/api/health field names and semantics before implementation.
- Use the
dborup/CoreScope releases URL.
- Verify the footer does not regress the drawer layout at narrow desktop/tablet widths.
- Decide separately whether the mobile
More surface needs parity; do not silently add a second eager health fetch.
Verification
- Unit coverage for success, rejected fetch, non-OK response, missing version, markup-shaped values and one-request caching.
- Browser verification at supported drawer viewports.
- Existing navigation and accessibility tests remain green.
No deploy is part of this issue.
Upstream source
Evaluate and port Kpa-clawbot/CoreScope#2068: show the running CoreScope version in the navigation drawer using the existing
/api/healthresponse.Intended behaviour
CoreScope <version>in the drawer footer./api/healthonly when the drawer is opened and only after its viewport/availability gate.CoreScopelabel rather than blank orundefinedtext.textContent; do not inject health fields as HTML.Fork-specific checks
/api/healthfield names and semantics before implementation.dborup/CoreScopereleases URL.Moresurface needs parity; do not silently add a second eager health fetch.Verification
No deploy is part of this issue.