chore: add vibetuner core-templates-path CLI for setup-tw-sources#1708
Merged
Conversation
Closes #1706. Replaces the inline ``python -c "import vibetuner; print(vibetuner.__path__[0])"`` dance in ``vibetuner-template/package.json``'s ``setup-tw-sources`` with a first-class CLI command. Output is plain stdout (logs go to stderr), so it's safe to use in shell command substitution. The updated ``setup-tw-sources`` also recovers from a stale ``.core-templates`` symlink: it resolves the canonical path via the CLI, compares it to the current symlink target via ``readlink``, and rebuilds only if the target has moved. Previously a venv rebuild that shifted the framework path could leave ``.core-templates`` pointing at a defunct location, silently dropping framework templates from Tailwind's ``@source`` scan. - New ``vibetuner core-templates-path`` command in ``vibetuner.cli``, printing ``package_templates / "frontend"`` (resolved, absolute). - Updated ``vibetuner-template/package.json`` ``setup-tw-sources`` to call the new command and check the existing symlink target before rebuilding. - Tests: stdout payload is exactly the path, single line, points at a real directory containing ``base/skeleton.html.jinja``. - Docs: new section in ``cli-reference.md`` and ``llms-full.txt``; ``llms.txt`` reference list updated. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
davidpoblador
pushed a commit
that referenced
this pull request
Apr 28, 2026
🤖 I have created a release *beep* *boop* --- ## [10.6.0](v10.5.0...v10.6.0) (2026-04-28) ### Features * enforce CSP in debug by default with opt-out flag ([#1702](#1702)) ([2d939ea](2d939ea)) * per-tenant theming via runtime CSS-variable injection ([#1707](#1707)) ([6a44e6c](6a44e6c)) ### Miscellaneous Chores * add `vibetuner core-templates-path` CLI for setup-tw-sources ([#1708](#1708)) ([b095d32](b095d32)) * **deps:** bump gitpython from 3.1.46 to 3.1.47 ([#1689](#1689)) ([b44149d](b44149d)) * **deps:** bump gitpython from 3.1.46 to 3.1.47 in /vibetuner-py ([#1688](#1688)) ([14aaf96](14aaf96)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #1706.
Summary
vibetuner core-templates-pathCLI command that prints the absolute path to the framework's frontend templates directory on a single line. Logs go to stderr; stdout is just the path, so it's safe in shell command substitution.vibetuner-template/package.json'ssetup-tw-sourcesto call the new command and verify the existing.core-templatessymlink target before rebuilding. Previously a venv rebuild that shifted the framework path could leave the symlink pointing at a defunct location, silently dropping framework templates from Tailwind's@sourcescan.base/skeleton.html.jinja.cli-reference.mdandllms-full.txt;llms.txtreference list updated.Smoke test
Verified locally that
setup-tw-sourcesis idempotent across three scenarios:.core-templates→ creates symlink..core-templatesat a wrong path → rebuilds correctly.Test plan
uv run python -m pytest tests/unit/test_core_templates_path_cli.py(4 new tests)uv run python -m pytest tests/(full suite, 721 passed)just format && just lint && just type-checkclean🤖 Generated with Claude Code