Skip to content

feat(home): show probing interpreter on family snapshot#59

Merged
silversurfer562 merged 2 commits into
mainfrom
feat/family-snapshot-interpreter-diagnostic
May 24, 2026
Merged

feat(home): show probing interpreter on family snapshot#59
silversurfer562 merged 2 commits into
mainfrom
feat/family-snapshot-interpreter-diagnostic

Conversation

@silversurfer562
Copy link
Copy Markdown
Member

Summary

  • The "Family snapshot" home tile sometimes shows attune-gui: Not installed for a package that is installed — the dashboard is just running under a different Python than the venv where the package lives.
  • This change surfaces sys.executable and the Python version under the section heading, so the env mismatch is self-diagnosing instead of mysterious.
  • API: /api/cowork/layers now returns interpreter and python_version alongside layers. Plumbed through build_home_summaryHomeSummary → template.

No behavior change for the happy path — when everything resolves correctly, the new caption just confirms which interpreter answered.

Test plan

  • uv run pytest sidecar/tests/test_cowork_health.py sidecar/tests/test_home_summary.py — 21 passed
  • Full sidecar suite (uv run pytest sidecar/tests/) — 544 pass; only unrelated pre-existing test_health_ok failure ('.' in 'dev', present on baseline main).
  • Visual check: load /dashboard after merge, confirm the "Probed under …" caption renders above the family cards.

🤖 Generated with Claude Code

silversurfer562 and others added 2 commits May 23, 2026 21:59
The "Family snapshot" tile sometimes renders "Not installed" for a
package that is installed in a venv — the dashboard is running under a
different Python. Surface sys.executable and the Python version under
the section heading so the env mismatch is self-diagnosing.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@silversurfer562 silversurfer562 merged commit 43c25eb into main May 24, 2026
5 checks passed
silversurfer562 added a commit that referenced this pull request May 25, 2026
attune-rag 0.2.0 shipped 2026-05-25 as the first SemVer-binding
cut — purely additive (new measure_corpus module + alias-file
helpers; no breaking API changes). The current core pin caps at
<0.2, silently locking fresh installs to attune-rag 0.1.23 even
when 0.2.x is available.

Widen the cap to <0.3 to unblock attune-rag 0.2.x installs.

The cap widen is the trigger for promoting the pending
[Unreleased] content to a real release. That content has been
queued on `main` since v0.7.1 (2026-05-22):

  - MCP server Phases 1-5 (PRs #49-#56) — new attune-gui-mcp
    console script with 6 tools (5 read-mostly + gui_set_spec_status
    write); 30+ tests across test_mcp_tools.py and
    test_mcp_integration.py
  - **Status:** parser fix (PR #57)
  - Living-docs regen automation Phase 1 (PRs #60-#63)
  - Home interpreter snapshot (PR #59)
  - Stacked-rebase README note (PR #58)

Bumped 0.7.1 → 0.8.0 (minor) for the new MCP tool surface.

Local smoke (python 3.10, fresh venv):
  pip install -e .[dev]
  → attune-gui 0.8.0, attune-rag 0.2.0
  545/545 sidecar tests pass (1 playwright skip, unrelated).
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.

1 participant