<feed xmlns='http://www.w3.org/2005/Atom'>
<title>newos4/skills/command-composition-rules.md, branch main</title>
<subtitle>newOS4 - the browser terminal that runs WebX11 user spaces</subtitle>
<id>https://newos.webx11.duckdns.org/newos4/atom?h=main</id>
<link rel='self' href='https://newos.webx11.duckdns.org/newos4/atom?h=main'/>
<link rel='alternate' type='text/html' href='https://newos.webx11.duckdns.org/newos4/'/>
<updated>2026-10-23T16:27:26+00:00</updated>
<entry>
<title>docs(newos4): merge the two shell-composition skills into one seeded skill (v4.6.65)</title>
<updated>2026-10-23T16:27:26+00:00</updated>
<author>
<name>Agando</name>
<email>roduccomm@gmail.com</email>
</author>
<published>2026-10-23T16:27:26+00:00</published>
<link rel='alternate' type='text/html' href='https://newos.webx11.duckdns.org/newos4/commit/?id=e74b3b1d8569c981cc34f1d5078fd19e8de98338'/>
<id>urn:sha1:e74b3b1d8569c981cc34f1d5078fd19e8de98338</id>
<content type='text'>
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).
</content>
</entry>
</feed>
