chamba 0.8.0 → 0.9.0

package/templates/webterm/tool-document.js

@@ -46,8 +46,8 @@ export function withNonce(html, nonce) {
  *
  * `default-src 'none'` is the floor, so anything not named below is refused. What runs is named by the nonce
  * alone. What is fetched is named by `origin` - the scheme and host the document was loaded from - because
- * the client's own assets, the tool's data routes and the jailed workspace files are all served from here,
- * and an opaque origin has no `'self'` to say that with. `base-uri` and `form-action` are named on their own,
+ * the client's own assets, its images and its clips, the tool's data routes and the jailed workspace files
+ * are all served from here, and an opaque origin has no `'self'` to say that with. `base-uri` and `form-action` are named on their own,
  * since neither one falls back to `default-src`.
  */
 export function documentPolicy(nonce, origin) {
@@ -56,6 +56,7 @@ export function documentPolicy(nonce, origin) {
         `script-src 'nonce-${nonce}'`,
         `style-src-elem 'nonce-${nonce}'`,
         `img-src ${origin}`,
+        `media-src ${origin}`,
         `connect-src ${origin}`,
         `frame-src ${origin}`,
         "base-uri 'none'",

package/templates/webterm/tools/home.js

@@ -0,0 +1,58 @@
+// =========================================================================================================================================
+// tools/home.js - What the Home tool is, as one table.
+//
+// The smallest table of the three, and the shape of a tool that only reads. There are no verbs, because Home has no helper and nothing
+// to say to an agent; no events, because it delivers nothing into a session; and no raw side, because it serves no file of the
+// workspace at all. What is left is three reads of the repository the workspace holds.
+//
+// The module is handed two directories rather than one: the workspace, which is the repository it draws, and the state directory
+// outside it, which is where its cache goes. The cache is derived from the repository and is nobody's record, so a file of it in the
+// workspace would show up in the `git status` of every repository Home opens. The module refuses a cache directory inside the
+// workspace, so the two can never be the same place.
+// =========================================================================================================================================
+
+import { createHomeModule, refuseRaw, statusFor } from "../../pane-apps/server/home.mjs";
+import { HOME_CACHE_DIR, HOME_KEY, HOME_RAW_TOKEN, MAX_HOME_BYTES, WORKSPACE, WORKSPACE_ROOT } from "../config.js";
+
+// The module maker, re-exported so the path to the built dist is written once, as it is for every tool.
+export { createHomeModule };
+
+export const HOME_TABLE = {
+    id: "home",
+    /** What a refusal calls the tool. The word on the tab is the client's own, in `tool-host.js`. */
+    label: "Home",
+    key: HOME_KEY,
+    rawToken: HOME_RAW_TOKEN,
+    statusFor,
+
+    /**
+     * The repository this draws, the directory outside it that the cache goes in, and the name to call it.
+     *
+     * The name is chamba's own for this workspace, which is what the bar wears, so the header row of the page and the corner of the
+     * window say the same word. Without it the header would show the mount point, which is "workspace" in every container there is.
+     */
+    create: () => createHomeModule({ root: WORKSPACE_ROOT, cacheDir: HOME_CACHE_DIR, name: WORKSPACE }),
+
+    /** Home delivers nothing into a session, so there is no sentence for one to arrive as. */
+    events: {},
+
+    /**
+     * How much a request may carry. Every route is a GET with no body, so nothing reaches this; it is here because the door that
+     * gates a body reads it for every tool, and a tool with no number is a tool with no gate.
+     */
+    limits: { bytes: MAX_HOME_BYTES },
+
+    /** Home serves no workspace bytes at all, so every path is refused rather than resolved. */
+    raw: (_module, path) => refuseRaw(path),
+
+    // The three reads, each one a section of the page. Three and not one: each costs what its own question costs, and the page draws
+    // each section the moment that section's answer lands.
+    routes: (module) => ({
+        history: { GET: () => module.history() },
+        branches: { GET: () => module.branches() },
+        tree: { GET: () => module.tree() },
+    }),
+
+    /** No verbs. The helper door is registered for every tool and answers 400 for every name it is given. */
+    verbs: () => ({}),
+};

package/templates/webterm/tools/index.js

@@ -5,15 +5,16 @@
 // types and how much of the typing channel one session gets. server.js reads the list and never a tool's name, so a third tool is
 // a row here and a table beside it.
 //
-// The order is the order the tabs are drawn in, which is the pane's own list in `public/app/pane-shell.js`. The two lists are
-// checked against each other by the interface's tests rather than derived from one another, because the pane is drawn in the
-// browser and this file is read in the server.
+// The order is the order the tabs are drawn in, which is the pane's own list in `public/app/pane-shell.js`, less Pages: the
+// interface draws that one itself and it has no table here. The two lists are checked against each other by the interface's tests
+// rather than derived from one another, because the pane is drawn in the browser and this file is read in the server.
 // =========================================================================================================================================
 
+import { HOME_TABLE } from "./home.js";
 import { REVIEWS_TABLE } from "./reviews.js";
 import { SPECS_TABLE } from "./specs.js";
 
-export const TOOLS = [SPECS_TABLE, REVIEWS_TABLE];
+export const TOOLS = [HOME_TABLE, SPECS_TABLE, REVIEWS_TABLE];
 
 /** The table of one tool, or undefined. Asked with `find`, so a name that is not a tool's is not one. */
 export function toolTable(id) {

package/templates/webterm/tools/reviews.js

@@ -4,8 +4,9 @@
 // The same shape as the Specs table beside it, and the differences are the tool's own. A review is a directory with a slug, so its
 // routes name their subject in the path rather than in a query, and the acts of the screen are one route with the act as a segment.
 // Its raw files are two named locations rather than any workspace file, so a browser reaches a stored blob and a signature and
-// nothing else. And it is the one module in this container that runs a child process, which is why it is handed the workspace as
-// well as its own root: every git call it makes runs with the repository as its working directory.
+// nothing else. And it is one of the two modules in this container that run a child process, Home being the other, which is why it
+// is handed the workspace as well as its own root: every git call it makes runs with the repository as its working directory. The
+// runner itself is shared, in the pane-apps server library, and this module hands it a closed table of read-only operations of its own.
 //
 // The framed sentences are the three acts that keep the review with the reviewer. Sending feedback, syncing and filing a review all
 // hand it over, and each of those types the review's command instead: the act starts the agent, and the skill reads the review's
@@ -111,7 +112,7 @@ export const REVIEWS_TABLE = {
         "review/:slug/blob": {
             GET: ({ params, query }) => module.blobLines(params.slug, field(query.name), count(query.from), count(query.count)),
         },
-        // One route for every act of FR-22 to FR-49. The module holds the list of them and refuses a name that is not one, so what
+        // One route for every act of a review. The module holds the list of them and refuses a name that is not one, so what
         // an act is stays in one place rather than being a row here as well.
         "review/:slug/:act": { POST: ({ params, body }) => module.act(params.slug, params.act, body) },
     }),
@@ -125,6 +126,9 @@ export const REVIEWS_TABLE = {
         // A review filed from the terminal, which the tab shows with a note saying so.
         start: (_entry, payload) => module.start(payload, "terminal"),
         metadata: (entry, payload) => module.metadata(entry, payload),
+        // One group at a time, which several workers may post at once without treading on one another.
+        group: (entry, payload) => module.group(entry, payload),
+        ungroup: (entry, payload) => module.ungroup(entry, payload),
         reply: (entry, payload) => module.reply(entry, payload),
         activity: (entry, payload) => module.activity(entry, payload),
         done: (entry) => module.done(entry),