skills: sanitize operator-identity tokens from folded ops skills

Four folded skills carried operator identity tokens that the sanitization
gate (verify-sanitized.sh) forbids in the public framework package:

- kickstart: template path pointed at a private brain checkout; now uses the
  framework-shipped $MOSAIC_HOME/templates/docs/TASKS.md.template
- mosaic-deploy: dropped one estate-specific stack-name row from the example
  table
- mosaic-portainer, mosaic-woodpecker: credentials now name the framework
  credentials store (load_credentials <service>) instead of a private
  checkout path

Estate-specific values can live in a skills-local override, which the linker
applies with precedence over canonical skills.
This commit is contained in:
fargo
2026-08-19 14:34:00 -05:00
parent 5e58597dbe
commit d2eeb64433
4 changed files with 7 additions and 8 deletions
@@ -166,13 +166,13 @@ Always load these orchestrator-relevant skills:
Create tracking files using templates:
```bash
TEMPLATES=~/src/jarvis-brain/docs/templates
MOSAIC_HOME="${MOSAIC_HOME:-$HOME/.config/mosaic}"
# Create tasks.md scaffold
envsubst < $TEMPLATES/orchestrator/tasks.md.template > docs/tasks.md
# Create tasks.md scaffold from the framework-shipped template
cp "$MOSAIC_HOME/templates/docs/TASKS.md.template" docs/tasks.md
# Create learnings tracking
envsubst < $TEMPLATES/orchestrator/orchestrator-learnings.json.template > docs/orchestrator-learnings.json
# Create learnings tracking (scaffold — adapt to your estate's template)
echo '{}' > docs/orchestrator-learnings.json
```
Then populate `docs/tasks.md` with tasks derived from the issues: