Skip to content

[spark-compete wave 1] install & build right - #304

Merged
vibeforge1111 merged 1 commit into
masterfrom
spark-compete/wave1-install-build
Jun 26, 2026
Merged

[spark-compete wave 1] install & build right#304
vibeforge1111 merged 1 commit into
masterfrom
spark-compete/wave1-install-build

Conversation

@vibeforge1111

Copy link
Copy Markdown
Owner

Spark Compete — Wave 1 ("install & build right")

Maintainer-consolidated Wave-1 PRs for this repo, from the Spark Compete audit.

Commits

  • fix: replace hardcoded Desktop path in registry DEFAULT_LAB_PATH [spark-character#28]

On-merge points (not written until merge)

johncrossu 7

Verification

python3 -m compileall -q src/spark_character/registry.py is clean. chip_loader.py left untouched (PR hunk dropped per maintainer note; HEAD already has the superior impl). git diff is exactly the single intended registry.py line change. No stray compete-*.json packet files at repo root. Full test/CI

Fraud/duplicate-split PRs excluded per ruleset v2. Draft — nothing merges or scores until reviewed.

🤖 Generated with Claude Code

registry.py DEFAULT_LAB_PATH hardcoded ~/Desktop/spark-personality-chip-labs/personalities,
which breaks installs that don't have the lab checked out on the Desktop. Switch the default
to the platform-safe ~/.spark/spark-personality-chip-labs/personalities location, consistent
with the search paths already prioritized in chip_loader.DEFAULT_CHIP_LAB_PATHS.

Narrowed from PR #28: the chip_loader.py hunk was dropped because HEAD already prioritizes
~/.spark/modules/... and ~/.spark/... ahead of Desktop and uses the stronger guard
'spark-personality-chip-labs' in path.parts (a better impl than the PR's 'in str(path)').
Only the still-unfixed registry.py one-line default is landed here.

Co-authored-by: johncrossu <johncrossu@users.noreply.github.com>
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@vibeforge1111
vibeforge1111 merged commit 786786d into master Jun 26, 2026
2 checks passed
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