Skip to content

chore: remove redundant sidecar/.help/ corpus#63

Merged
silversurfer562 merged 1 commit into
mainfrom
chore/remove-redundant-sidecar-help-corpus
May 24, 2026
Merged

chore: remove redundant sidecar/.help/ corpus#63
silversurfer562 merged 1 commit into
mainfrom
chore/remove-redundant-sidecar-help-corpus

Conversation

@silversurfer562
Copy link
Copy Markdown
Member

Summary

sidecar/.help/ was an early auto-scaffold that never got curated and duplicates the root .help/ corpus entirely. Removing it.

Why it's safe

Overlap analysis:

sidecar/.help/ feature What root .help/ already covers
attune-gui (files: attune_gui/**) Strict subset of root's sidecar (files: sidecar/**)
attune_gui-entry (attune_gui/app.py) Duplicate — root has the same entry at sidecar/attune_gui/app.py
attune-gui.egg-info Build artifact, not source; should never have been a feature
tests (tests/**) Covered by root's sidecar/** glob

Runtime impact: none. living_docs_store.py:241,386,436 and commands.py:207-302 resolve .help/ via project_root. The federated config (~/.attune-gui/config.json) sets workspace = /Users/patrickroebuck/attune-gui — the repo root. Runtime reads root corpus only.

Egg-info note: sidecar/.help/features.yaml defined attune-gui.egg-info as a feature with files: attune-gui.egg-info/**. egg-info is build metadata — definitely never a documentation target. Confirms this corpus was a stale auto-scaffold, not a curated home.

Also dropped

The Makefile's regen-templates comment that documented the sidecar corpus as "deferred and not maintained here" — no longer accurate since it doesn't exist to defer.

Test plan

  • grep -rn "sidecar/.help" finds no remaining references (only the now-removed Makefile comment)
  • All runtime .help/ reads resolve via project_root (verified in living_docs_store.py, commands.py, cowork_files.py)
  • CI green

🤖 Generated with Claude Code

sidecar/.help/ was an early auto-scaffold from a stale-era
'attune-author init' inside sidecar/. It was never curated and
duplicates the root .help/ corpus entirely:

- Its 'attune-gui' feature (attune_gui/**) is a strict subset of
  root's 'sidecar' feature (sidecar/**).
- Its 'attune_gui-entry' feature points at the same file root's
  does (sidecar/attune_gui/app.py).
- Its 'attune-gui.egg-info' feature is a build artifact, not source.
- Its 'tests' feature is covered by root's broader sidecar/** glob.

The runtime never reads sidecar/.help/ — living_docs_store.py,
commands.py, and cowork_files.py all resolve .help/ via
project_root, which the federated config sets to the repo root.

Also drops the now-obsolete Makefile comment explaining why the
sidecar corpus was deferred — it no longer exists to defer.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@silversurfer562 silversurfer562 merged commit 71f2a99 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