Standalone binary distribution, forgejo-mcp pin fix, allow-list/deny-list terminology (v0.3.0) #1
Loading…
Reference in a new issue
No description provided.
Delete branch "goern/castra:main"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Brings
agentic-forges/castraup to date with the work ongoern/castra, and cuts the surface needed for av0.3.0release.Contents
forgejo-mcpto thev2.30minor series (compare major.minor) so patch releases pass while a minor bump still fails loud; an empty--clistdout now reports the tool's real error instead of blaming the version pin;selftestpicks its default target per forge hostCASTRA_HOMErather than the clone, so a lane can triage an issue whose code lives in another checkoutlist-terminologypre-commit hook and recorded inAGENTS.mdinstall.sh(curl-pipe, checksum-verified),scripts/release-build.sh(cross-compiles linux-x64, linux-arm64, darwin-arm64),install:local/release:buildscripts; version 0.3.0Note on history
Upstream
maincarries719b622; this branch replaces it withdb07c53— the same tree and message, re-signed with the correct key. The merge will therefore show that change twice. Content is identical, so no conflict is expected.204 tests pass; biome, typecheck and the terminology hook are green.
Persona prompts said `Read .agents/skills/<name>/SKILL.md`, resolved against the cloned target repo. A repo shipping no skills of its own therefore gave the agent no method and no output contract — it would improvise an off-schema verdict or trip the gate. code/fix papered over this by seeding skills into the checkout with `cp -rn`; intake had no seeding at all and simply broke. - castraSkills() mirrors castraHome(): CASTRA_SKILLS > <cwd>/.agents/skills > CASTRA_SKILLS_FALLBACK > /opt/castra/.agents/skills — the target repo's own skills still win, the image copy is the fallback - renderPrompt() binds {{SKILLS}} to that absolute path; unbound still shows up in the existing unresolved-placeholder warning - persona-run resolves against the persona's workingDir, not castra's cwd — the agent runs in the clone, not here - retire the duplicated `cp -rn` seeding from castra-code/castra-fix Verified across all three branches: skill-less dir → image fallback, castra itself → its own tree, CASTRA_SKILLS → the override. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>