mosaicstack/stack
25
0
Fork 1
Code Issues 415 Pull Requests 13 Actions Packages Projects Releases 15 Wiki Activity

harness: README names bundle-refused for the skill content refusals, skill-refused at the launcher (row 64 F1, #1557 comment 29218)

Browse Source
This commit is contained in:
jason.woltje
2026-10-19 16:11:42 -05:00
parent 9f00397110
commit 6b6567b8b4
1 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
packages/harness/README.md
+6 -5
View File
@@ -52,11 +52,12 @@ so an existing bundle is never overwritten):
`skillsDir` (`<dataRoot>/skills-enabled`, which `scripts/skill.sh
activate` fills). The prompt text is read from the copy, so a skill
deactivated after the build leaves the run's copy as it was. A listed
skill that isn't enabled refuses `skill-not-enabled`. So does a symlinked
skill, `SKILL.md` or sub-file, a file name outside `[A-Za-z0-9._/-]`,
non-UTF-8 bytes, a file holding `</skill-file>`, or a role whose skills
add up to more than `SKILL_BYTES` (64 KiB; the prompt goes to the harness as
one argv argument, and Linux caps one argument at 128 KiB).
skill that isn't enabled refuses `skill-not-enabled`. A symlinked skill,
`SKILL.md` or sub-file, a file name outside `[A-Za-z0-9._/-]`, non-UTF-8
bytes, a file holding `</skill-file>`, or a role whose skills add up to more
than `SKILL_BYTES` (64 KiB; the prompt goes to the harness as one argv
argument, and Linux caps one argument at 128 KiB) refuses `bundle-refused`,
which the launcher reports as `skill-refused`.
- `policy.json`: harness, workspace, built-in tools (`limits.tools`), typed
tool names, network, the services the role needs, and the credential
status the host read from the broker (metadata only, never a token).