release/0.2.0#17
Open
A wants to merge 8 commits into
Open
Conversation
…tier + home_dir vault resolution Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…command + create-project seeding + docs Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
… vault resolution + test home isolation vault-commit/frontmatter-update/transition resolved the vault via bare Project.load_cwd(), ignoring the configured home_dir; Context.assemble and the commands now share Project.load_cwd_configured(). Test suite additionally isolates HOME so no run writes outside tmp. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…playbook framework — context models, /playbook skill, docs
…worked example in playbooks docs
The repo-root `.booping` marker is gitignored, so it is absent in CI checkouts. The test relied on chdir-ing to the real repo root to resolve a project (hence a vault under the tmp HOME); without the marker, Project.load_cwd returned None, the log write was skipped, and the `home/Claude` assertion failed. Build a self-contained repo dir with its own `.booping` marker and isolate XDG_CONFIG_HOME instead. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.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.
Global config tier +
home_dirBooping now reads a global config at
${XDG_CONFIG_HOME:-~/.config}/booping/config.yaml, deep-merged between the core defaults and the per-project tier (core → global → project, same shallow-merge semantics foragents).The headline key is
home_dir— the vault-home base (default~/Claude/) is no longer hardcoded. Vault resolution precedence:.boopingvault_path:> globalhome_dir> core default; ahome_dirset in the project tier is a documented no-op. Path expansion happens in a single site (_resolve_vault_dir), so config surfaces always display the raw value the user wrote.Also in this feature:
booping config-get <dotted.key>subcommand — scalars print raw, mappings/lists print YAML, missing keys exit 1; works outside any attached project.booping-create-projectresolves its vault root through a deterministic ladder (global config → existing~/Claude→ interactive prompt) and seeds the global config on true first run; non-interactive unresolvable runs abort with instructions instead of silently scaffolding.transition,vault-commit,frontmatter-update) share the same configured resolution viaProject.load_cwd_configured().XDG_CONFIG_HOME+HOMEpinned to tmp dirs).Second release feature coming to this branch before the release is cut.
🤖 Generated with Claude Code