feat(skills): add mempalace proactive-load directive for containers
Baking the mempalace fallback skill fixed *availability*, but mempalace had no proactive-load directive anywhere (pi-toolkit's global AGENTS.md only points to pi-extensions), so a new container would still surface it only via description-matching — the same under-utilisation the pi-extensions directive was created to fix. Add a session-start pointer to the pi-devbox managed AGENTS.md block (pi-global-AGENTS.append.md): gated to pi-devbox containers and conditional on the MemPalace MCP tools being present. Memory continuity matters most in a frequently-recreated container — the palace is its only cross-recreate memory. - pi-global-AGENTS.append.md: '## Session start: load the mempalace skill'. - smoke-test: assert the pointer merges into the global AGENTS.md at build. - docs: VENDORED.md, README, CHANGELOG [Unreleased]. Now both skills are complete in pi-devbox: directive + skill file. pi-extensions = directive (pi-toolkit) + baked skill; mempalace = directive (this block) + baked skill.
This commit is contained in:
@@ -22,6 +22,15 @@ Pre-v1.0.0 tags followed the pi npm version (`v{pi_version}[letter]`).
|
||||
the private `skillset` repo mounted. The image now bakes fallback copies of
|
||||
both skills under `/usr/local/share/pi-devbox/skills/`, symlinked in by
|
||||
`entrypoint-user.sh` (only when absent, so a mounted skillset still wins).
|
||||
- **Proactive-load directive for `mempalace`.** Baking the skill only fixes
|
||||
*availability*; nothing in pi-toolkit's global `AGENTS.md` told sessions to
|
||||
load it, so it would still surface only via description-matching. The
|
||||
pi-devbox managed block (`pi-global-AGENTS.append.md`) now adds a
|
||||
session-start pointer (gated to pi-devbox containers, conditional on the
|
||||
MemPalace MCP tools being present) so a new container actually picks the
|
||||
skill up — memory continuity matters most in a frequently-recreated
|
||||
container. (`pi-extensions`'s directive already ships in pi-toolkit, so only
|
||||
its skill file needed baking.)
|
||||
- **Layered freshness for the `pi-extensions` skill (Option 1 + Option 2).**
|
||||
The canonical skill was promoted into the **public `pi-extensions` package
|
||||
repo** under `skill/` (co-located with the extensions it documents). A
|
||||
|
||||
Reference in New Issue
Block a user