diff options
Diffstat (limited to 'help.html')
| -rw-r--r-- | help.html | 21 |
1 files changed, 20 insertions, 1 deletions
@@ -244,6 +244,7 @@ footer .tagline{color:var(--accent2);margin-top:10px;font-weight:500} <a href="#overview" class="nav-link">Overview</a> <a href="#start" class="nav-link">Quick Start</a> <a href="#commands" class="nav-link">Commands</a> + <a href="#guides" class="nav-link">Guides</a> <a href="#filesystem" class="nav-link">Filesystem</a> <a href="#ai" class="nav-link">AI Agent</a> <a href="skills.html" class="nav-link">Skills → dynamic</a> @@ -587,6 +588,22 @@ diff a.txt b.txt</pre> </section> <!-- ── Filesystem ── --> + <section id="guides"> + <h2>📚 Guides</h2> + <p>Long-form guides live in the VFS under <code>/guides/</code>. The AI writes them there; you can + reach them three ways:</p> + <ul> + <li><code>guides</code> — list what exists, newest first (this is the index that did not exist before v4.6.63)</li> + <li><code>preview <name></code> — render an HTML guide in the preview pane</li> + <li><code>cat <name></code> — read a markdown guide as text</li> + </ul> + <p>Published guides on this server:</p> + <ul> + <li><a href="../agando/guides/newos-future.html">newOS4 — future directions</a></li> + <li><a href="../agando/guides/request-to-newos4-team.md">Request to the newOS4 team (2026-10-23)</a></li> + </ul> + </section> + <section id="filesystem"> <h2>📁 Filesystem</h2> <p>All VFS files persist in <code>localStorage</code>. <code>ls</code>, <code>cd</code>, <code>pwd</code> work like a real terminal. Clickable output — tap a file to <code>cat</code>, tap a dir to <code>cd</code>.</p> @@ -1672,13 +1689,15 @@ listmods</pre> <h2>📋 Changelog</h2> <div class="version-item"> - <div class="v-header"><span class="v-num">v4.6.57–62 — October 2026</span><span class="v-date">2026-10-23</span></div> + <div class="v-header"><span class="v-num">v4.6.57–63 — October 2026</span><span class="v-date">2026-10-23</span></div> <ul> <li><strong>No shell — and it now says so</strong> — <code>;</code>, <code>&&</code> and <code>||</code> are refused with an explicit message instead of being folded into the command's argv (where <code>wc -l f && grep -c x f</code> returned a plausible wrong number). A <code>|</code> arriving from the AI <code>run_command</code> tool is refused too, because that path bypasses the pipe splitter and degraded the pattern to empty. Documented at the top of the command reference.</li> <li><strong>Multiple paths in <code>wc</code></strong> — <code>wc -c a b</code> printed only <code>a</code> and exited clean. It now prints one line per file plus a <code>total</code>, and reports each missing file separately.</li> <li><strong><code>ls</code> prints text</strong> — it rendered only clickable chips (DOM-only), so any capture — the AI <code>run_command</code> tool, the diagnostics sweep — saw an empty result and reported "directory empty".</li> <li><strong><code>view_module</code> shows what is deployed</strong> — it returned the <code>_mods/<Class>.js</code> edit cache first, unversioned, so after a rebuild it showed pre-fix source while the bundle was new. It now fetches the deployed file and prefixes the version; the cache is a labelled fallback.</li> <li><strong><code>load_skills</code> searches tokens, not one phrase</strong> — the query used to be tested whole against name+description+tags, so <code>"telemetry dashboard"</code> returned 0 while <code>"telemetry"</code> returned 1, and a sentence could never match. Skill <em>bodies</em> were never searched. It now tokenises (stopwords dropped), scores name > description/tags > body, weights by how many tokens matched, keeps a phrase bonus so word order cannot zero a real hit, and reports <code>matchedTokens: 2/3</code> with each result.</li> + <li><strong>Agent status says what it means</strong> — four agents showed <code>sleeping</code> with no way to tell "waiting for work" from "never handed a task". They now read <code>parked — NEVER SCHEDULED (0 tasks since …)</code> or <code>waiting for work (3 tasks, last …)</code>, plus a dispatch line and a warning when spawning happened but nothing was ever dispatched.</li> + <li><strong>A guide you can actually find</strong> — <code>guides</code> lists <code>/guides/</code> newest-first; the help page has a Guides section with the command, the preview/cat hints and links to published guides.</li> <li><strong>One error counter</strong> — <code>errors</code>, <code>get_dashboard_data</code> and the world model tallied three different sinks (0 / 18 / 11 in the same second). All three now read <code>terminal.countErrors()</code> (DebugSupervisor DB + failed tool calls); the VFS log is reported separately as a mirror, and <code>terminal.log('ERROR', …)</code> now records into the same DB instead of a second store nobody read.</li> <li><strong>Predictor arithmetic</strong> — the stored field named <code>mape</code> held a sum, so any JSON consumer read a mean that was <em>n</em> times too large (now <code>errorSum</code>); <code>errorPct</code> is stored raw and clamped only at render (a 475× miss used to be flattened to 500%); predictions are floored at 1 s and floor-hits are not scored, because one 0.079 s aborted run was rounding the next prediction to 0 s.</li> </ul> |