diff options
| author | Agando <roduccomm@gmail.com> | 2026-10-23 18:27:26 +0200 |
|---|---|---|
| committer | Agando <roduccomm@gmail.com> | 2026-10-23 18:27:26 +0200 |
| commit | 87f44c42aeb763e2aaf3da159d60b252dca9aa53 (patch) | |
| tree | 8a2718d191504d694ac187d47e7cdc77a5695d45 /modules/ext/finder.js | |
| parent | 9c27d3790b594c94430015675c91ce618c61be1d (diff) | |
docs(newos4): merge the two shell-composition skills into one seeded skill (v4.6.65)
Packet 9. `terminal-commands-silently-failing` and `command-composition-rules` described
the same bug family from two angles, and since v4.6.58 both were describing behaviour
that is now refused outright.
- new seeded skill `command-composition-rules` in skill-pack-core's _buildSkills():
the rule, why the refusal exists (with the 42-42 / 34k-a measurement), what works
(one command per call, wc multi-path, interactive-only pipes, quoted operators),
how to verify a plausible-looking result, and the pitfalls
- its History section names both retired skills so a reader arriving from either
search finds the surviving one
- mirrored onto disk as skills/command-composition-rules.md + .json and added to
skills/index.json (18 entries) so the repo copy matches what sessions receive
Verified live on v4.6.65: seeding reported 15 skills (was 14), the file and index
entry exist in the fresh VFS, and the natural-language query "does the terminal have
a shell and what is refused" returns command-composition-rules first (13.78, 3/4).
Diffstat (limited to 'modules/ext/finder.js')
0 files changed, 0 insertions, 0 deletions