@timqi/pier 0.1.0 → 0.1.1

package/skills/pier-boards/SKILL.md

@@ -5,10 +5,9 @@ description: Publish a Board — a folder of static HTML Pier serves at a stable
 
 # Building a Pier board
 
-A **board** is a directory in the boards folder `<pier>/AGENTS.md` names under
-"This Pier instance" — use that path verbatim; `~/.pier` is only the default.
-Pier serves `<board>/site/` and nothing else. Boards outlive sessions: any
-session may read or rewrite any board, and closing this one changes nothing.
+A **board** lives in the exact boards folder named under "This Pier instance"
+in `<pier>/AGENTS.md`; do not assume `~/.pier`. Only `<board>/site/` is served.
+Boards survive sessions; any session may read or update them.
 
 ## Create one
 
@@ -27,13 +26,9 @@ session may read or rewrite any board, and closing this one changes nothing.
 }
 ```
 
-Those four fields are the whole manifest (publishing adds a fifth — below).
-
-- `slug`: `[a-z0-9][a-z0-9-]{0,63}`, and it is the URL — short and stable. Do
-  not add random characters of your own; publishing adds them (see below).
-- `description` is the Console list entry: write it for someone who has
-  forgotten this conversation.
-- `sessions`: append your own id, never replace — other ids are provenance too.
+- `slug`: `[a-z0-9][a-z0-9-]{0,63}`; keep it short and stable, without random suffixes.
+- `description`: Console list text, understandable without this conversation.
+- `sessions`: append your id; preserve others as provenance.
 
 ## Publish, then hand over the link
 
@@ -42,40 +37,25 @@ asked for a public or shareable board *in this request*; otherwise leave it
 `false` and say the board is private. Never publish personal data or anything
 the user has not seen.
 
-The published address is `/p/<slug>-<token>/`, not `/p/<slug>/`, so a public
-board's URL cannot be guessed from its name. `token` is a fifth manifest field
-you write next to `"public": true` — eight hex characters from
-`openssl rand -hex 4`, never invented in your head, never reused between
-boards. Leave it out and Pier mints one on the first request, but then the link
-is only visible in the Console, so write it yourself and you can hand it over
-in the same message.
-
-Asked to make an existing board public? Set `"public": true` and a fresh
-`token` in `board.json`, then reply with the `/p/<slug>-<token>/` link — that is
-the whole answer. Already has a token? Keep it: the link may be out there. No
-verification step, no narrating the edit, no restating what the page holds.
-
-The message announcing the board carries **one bare URL** — paste the address
-itself, never `[title](url)`: link labels get mangled or truncated on some chat
-surfaces, and the title is already on the page. No filesystem paths either —
-`…/boards/<slug>/board.json` means nothing to the reader.
-`<pier>/AGENTS.md` gives you the address, so there is nothing to look up:
-
-| The user asked for | Send |
+For publishing, preserve the manifest's `token` or add eight hex characters
+from `openssl rand -hex 4`; never invent or reuse another board's token.
+
+Use the instance address from `<pier>/AGENTS.md` plus:
+
+| Visibility | Path |
 | --- | --- |
-| a board, nothing about sharing | `https://pier.example.com/boards/weekly-digest/` — behind the Pier password; Console → Boards makes it public |
-| a **public** board | `https://pier.example.com/p/weekly-digest-3f9ac128/` — no password; the suffix is the manifest's `token`, copied verbatim |
+| Private (default) | `/boards/<slug>/` — password required; Console → Boards can publish |
+| Public | `/p/<slug>-<token>/` — copy the token verbatim; 404 unless `public: true` |
 
-Never both: the pair invites pasting the password-free URL of a board that was
-never meant to leave the workspace, and `/p/<slug>-<token>/` 404s unless the manifest
-says `"public": true`. No address configured? Give the path, say Console →
-Settings turns it into a link, and never guess a host.
+Return **one bare URL**, never both, Markdown link labels or filesystem paths.
+If no address is configured, give the path and point to Console → Settings;
+never guess a host. For a publish-only request, set `public: true` and a token
+if missing, then return only the public URL; no page verification or narration.
 
 ## Writing the page
 
-A board is a **presentation**, not a text file: someone opens it to get an
-answer fast. Link the shipped stylesheet and write plain semantic HTML — no
-build, no npm, no framework:
+Let the question and evidence determine layout; no sections are required.
+Use semantic HTML without a framework. Adapt this shell's language and content:
 
 ```html
 <!doctype html>
@@ -87,143 +67,84 @@ build, no npm, no framework:
 <link rel="stylesheet" href="/p/_assets/pier.css">
 </head>
 <body>
-<div class="hero">
-  <h1>Weekly digest — infra</h1>
-  <p class="lede">Throughput is up, but two migrations need a decision before Friday.</p>
-  <p class="muted">18 Feb 2026 · covers 12 repos</p>
-</div>
-
-<div class="grid">
-  <div class="card"><span class="kpi good">12</span> PRs merged <span class="muted">+3 vs last week</span></div>
-  <div class="card"><span class="kpi warn">2</span> awaiting decision</div>
-  <div class="card"><span class="kpi">98.9%</span> uptime <span class="muted">30 d</span></div>
-</div>
-
-<div class="callout warn">
-  <strong>Needs you:</strong> the payments migration blocks two teams — approve or defer by Friday.
-</div>
-
-<h2>Payments is the only degraded service</h2>
-<table>
-  <thead><tr><th>Service</th><th>Status</th><th class="num">p95</th><th>Error budget</th></tr></thead>
-  <tbody>
-    <tr><td><strong>payments</strong></td><td><span class="tag bad">degraded</span></td><td class="num">910 ms</td>
-        <td><span class="bar bad" style="--v:18%"></span></td></tr>
-    <tr><td>api</td><td><span class="tag good">healthy</span></td><td class="num">142 ms</td>
-        <td><span class="bar good" style="--v:82%"></span></td></tr>
-  </tbody>
-</table>
-
-<details><summary>All 12 merged PRs</summary>
-<table><thead><tr><th>PR</th><th>Author</th><th>Merged</th></tr></thead>
-<tbody><tr><td>#412</td><td>ana</td><td>Mon</td></tr></tbody></table>
-</details>
-
-<footer>Written by Pier · data as of 18 Feb 09:00 · ask for an update to refresh</footer>
+<h1>Weekly digest — infra</h1>
+<p class="lede">The main finding, grounded in the available evidence.</p>
+<footer>Data as of … · sources … · how to refresh …</footer>
 </body>
 </html>
 ```
 
-What makes it read as designed rather than generated:
-
-- **The lede is the verdict, not the topic.** "Two migrations need a decision by
-  Friday" answers; "This digest covers infra activity" restates the prompt. A
-  reader who stops after the hero must still leave with the point.
-- **Headings are findings.** "Payments is the only degraded service", not
-  "Services". A heading that could top any report — Overview, Summary, Details —
-  says nothing about this one.
-- **Every number carries its unit and its baseline**: "142 ms p95, was 120",
-  "12 of 40". A bare number is decoration; so is fake precision (98.8724% →
-  98.9%).
-- **End at the last useful block.** No closing summary, no filler section. The
-  footer holds provenance: data as-of, source, how to refresh.
+Lead with the verdict; headings state findings ("Payments alone is degraded").
+Numbers carry units and baselines ("142 ms p95, was 120", "12 of 40"), without
+false precision. End without filler or a closing summary; put the data
+timestamp, sources and refresh instructions in the footer.
 
 ## What `pier.css` gives you
 
-Headings, paragraphs, lists, tables, `pre`/`code`, `blockquote`, `details` and
-`footer` are styled with **no classes at all**, dark mode included. The page
-sizes itself: a wide desktop canvas (62rem, 76rem on a very large screen) that
-reflows to one column on a phone, prose held to a readable measure while tables,
-`.grid`, `.split` and `.hero` use the full width — don't add a `max-width` of
-your own. Zebra striping, tables that scroll inside themselves, and `<details>`
-that print open are free. On top of that:
+Classless defaults include readable prose, responsive widths, dark mode,
+scrolling zebra tables and print styles. Override widths only as needed.
 
 | Class | Use it for |
 | --- | --- |
-| `.lede` | the one-sentence answer under the title |
-| `.hero` | the opening block: title + lede + date/scope, on a tinted panel |
-| `.grid` + `.card` | a KPI row (auto-fits to one column on a phone) |
-| `.kpi` | the headline number inside a card |
-| `.card` + `.good/.warn/.bad/.info` | a status card: accent edge and tinted fill |
-| `.callout` (`.good` `.warn` `.bad`) | the takeaway or the ask |
-| `.tag` (`.good` `.warn` `.bad` `.info`) | status pills in tables and lists |
-| `.good` `.warn` `.bad` | colour on a number or a word |
-| `.num` | right-aligned, tabular numeric table cells |
-| `.bar` (`.good` `.warn` `.bad`) | share-of-total inside a table: `style="--v:62%"` |
-| `.split` | two columns that stack on a phone: before/after, text + aside |
-| `.muted` | secondary text: dates, deltas, units, scope |
-
-Need something it lacks? A `<style>` block or your own CSS file inside `site/`
-is normal, and so is a custom colour or a hand-written layout when the content
-calls for one.
+| `.lede` / `.hero` | opening answer / tinted opening panel |
+| `.grid` + `.card` + `.kpi` | responsive cards with headline numbers |
+| `.callout` / `.tag` | takeaway or ask / status pill |
+| `.num` | right-aligned tabular numbers |
+| `.bar` | proportion: `style="--v:62%"` |
+| `.split` | two columns, stacking on phones |
+| `.muted` | dates, deltas, units, scope |
+
+Status modifiers: `.good` healthy/done, `.warn` attention/pending, `.bad`
+broken/blocked; express status in words too. These colour text, cards,
+callouts, tags and bars; cards and tags also accept `.info` for neutral emphasis.
+All helpers are optional. Custom `<style>` or CSS under `site/` may change
+layout and palette while preserving contrast and phone reflow.
 
 ## Pick the form from the content
 
-| What you have | How to present it |
+| Content | Possible form |
 | --- | --- |
-| The single most important fact | `.hero` lede, or one `.kpi` on its own |
-| 2–4 headline metrics | `.grid` of `.card`s, each with `.kpi` + a `.muted` delta |
-| Something the reader must act on | `.callout warn` near the top, naming the deadline |
-| Items with a state | table with `.tag` pills, worst rows first |
-| Ranked or compared numbers | table, `.num` columns, `.bar` for share of total |
-| Progress toward a goal | `.bar` per row, or `.kpi` + "of 40 done" in `.muted` |
-| Two alternatives | `.split` with a `.card` each, verdict in the lede above |
-| A sequence of events | ordered list, date in `.muted` at the start of each item |
-| A trend over time | first/last + delta in words; inline SVG only if the shape *is* the news |
-| 200 rows | aggregate, show the 5–10 that matter, rest in `<details>` with the count in its summary |
-| 1–2 data points | a sentence or a `.callout` — a one-row table is a table costume |
-| Long raw output, logs, code | `<details>` at the bottom, or `<pre><code>` trimmed to the lines that matter |
-| Nothing to report | say so in the lede ("all 14 checks green") and stop — short is finished, not thin |
-
-Vary the forms: never two blocks of the same kind in a row, and prefer number →
-ask → proof → fold over six paragraphs. A status or decision board earns one
-screenful before the first `<details>`; only a handover or postmortem earns a
-long scroll. Colour is part of the message — green healthy/done, amber
-attention/pending, red broken/blocked, `.info` neutral emphasis — on the numbers
-and status cells that carry the point, never on ordinary prose; that contrast is
-what makes it read as signal.
+| One finding or 1–2 values | sentence; if nothing changed, say so and stop |
+| Headline metrics | KPI cards with deltas; progress includes the total |
+| Required action | prominent ask with deadline |
+| States, rankings or shared comparison criteria | table; worst states first |
+| Alternatives needing separate explanations | parallel sections; recommendation first |
+| Events / trends | dated list / endpoints and delta; chart when shape explains the finding |
+| Large datasets or raw output | aggregate, show relevant rows, fold the rest with a count; trim code/logs |
+
+Repeat forms for comparable items; vary them when information changes. Put
+findings and actions first, then evidence; fold only supplementary detail.
 
 ## Rules
 
-- **No secrets, ever.** Tokens, API keys, credentials, internal hostnames and
-  private paths never go into a board — not in the page, not in a `<details>`
-  fold, not in a code sample. A private board is one Console toggle from
-  public, so write every page as if it already were.
-- **Static and self-contained.** Everything the page needs lives under `site/`
-  with relative paths. No CDN, no external fonts, no analytics, no `fetch()` —
-  a published board is served under a CSP that blocks all of it, so an external
-  reference is a broken page, not a slow one.
-- **Content, not an app.** Interaction is `<details>` and anchors; the page
-  stays readable with JavaScript off.
-- **Show, don't narrate.** A sentence describing numbers should have been a KPI
-  row or a table. Prose is for judgement — what it means, what to do.
-- **Structure before graphics.** A chart is inline SVG (no library) and only
-  when the *shape* of the data is the message. A three-row table beats any
-  picture of three numbers; no chart beats a decorative one.
-- **Only real data.** Every figure traces to something you saw this session, and
-  a gap is shown as a gap ("no data since Tue", "~3 weeks", "n=3") — never
-  smoothed into a clean number.
-- **Rewrite in place.** Updating a board means editing its files, not creating
-  `weekly-digest-v2`. The URL is the point.
-- Top-down — what this is → the answer → detail → raw data in `<details>` —
-  prose in the user's language, short headings, no emoji chrome.
+- **No secrets:** no tokens, API keys, credentials, internal hostnames or
+  private paths in page content, including folds and code samples; private
+  boards can become public with one Console toggle.
+- **Self-contained:** assets live under `site/` with relative paths, except
+  the shipped stylesheet; no CDN, external fonts, analytics or `fetch()`
+  (blocked by the public CSP).
+- **Interaction:** prefer `<details>` and anchors; local JS may sort, filter or
+  inspect embedded data, without network calls or server runtime. With JS off,
+  keep the answer and evidence readable; hide or disable unavailable controls.
+- **Charts:** use when data shape explains the finding; prefer inline SVG,
+  a small bundled library only for needed interaction, with text/table fallback.
+- **Real data:** every figure traces to evidence seen this session; expose
+  gaps and uncertainty ("no data since Tue", "~3 weeks", "n=3").
+- **Update in place:** edit the existing board; preserve its URL.
+- Write in the user's language, with short headings and no emoji chrome.
+
+## Check the page
+
+For new pages or layout/interaction changes, run the checks below; for content
+edits, check the affected content and links. Report actual coverage or gaps.
+
+- Phone/desktop, light/dark: readable contrast, no page overflow, tables scroll internally.
+- Keyboard/touch: working links and controls, visible focus, usable targets, text status labels.
+- Assets load without console errors; answer and evidence remain readable with JS off.
 
 ## If a board needs a build
 
-Pier ships no toolchain and the default is no build. If one is genuinely needed
-(a bundled charting library, a component layout), you own it: keep sources
-outside `site/` (e.g. `<board>/src/`), emit into `site/`, and write a
-`<board>/README.md` a future session can follow cold — install command, build
-command, output path, where the data came from. Never leave `site/`
-inconsistent with its sources; on an existing board look for that README first
-and rebuild, because hand-patching `site/` is lost on the next build.
+Pier ships no toolchain. If a build is needed, keep sources outside `site/`,
+emit into `site/`, and document install/build commands, output path and data
+sources in `<board>/README.md`. Before editing an existing board, check for
+that README; update sources and rebuild so `site/` stays consistent.

package/skills/pier-help/SKILL.md

@@ -6,15 +6,15 @@ description: How Pier itself works — durable sessions, what survives a restart
 # How Pier works
 
 Pier is the workspace this session runs in: agent sessions behind chat
-surfaces — a web workbench and IM channels (Slack and Telegram today) — plus
-scheduled tasks, subagents and boards. Answer questions about it from the
-facts below. If the answer is not here, say you do not know how this instance
-is configured rather than guessing: the Console (Pier's admin web UI) is the
-operator's source of truth.
+surfaces — a web workbench and IM channels (Slack, Telegram, Lark) — plus
+scheduled tasks, subagents and boards. Answer from the facts below. If the
+answer is not here, say you do not know how this instance is configured rather
+than guessing: the Console (Pier's admin web UI) is the operator's source of
+truth.
 
 ## Sessions and persistence
 
-- One durable session per conversation: a web chat, a Slack thread, a
+- One durable session per conversation: a web chat, a Slack or Lark thread, a
   Telegram chat or topic. The mapping survives restarts — the next message
   lands in the same transcript with its context intact.
 - Idle sessions leave memory but keep their transcript; they resume
@@ -48,7 +48,8 @@ operator's source of truth.
   into the running turn as a steer.
 - From an IM chat, every mid-turn message steers the running turn directly —
   no `!` needed, and a leading `!` is just content.
-- `/stop` aborts the current turn outright.
+- `/stop` from an IM chat aborts the current turn outright; the web has a Stop
+  button.
 
 ## In-chat commands and the settings panel
 
@@ -61,12 +62,13 @@ operator's source of truth.
 
 ## What a turn looks like from outside
 
-- Telegram and Slack put a 👀 on the message that started a turn and take it
-  off when the turn settles; a restart and a periodic sweep clear stragglers.
+- IM channels put a 👀 (Lark: "OnIt") on the message that started a turn and
+  take it off when the turn settles; a restart and a periodic sweep clear stragglers.
   A 👀 that never clears means the turn died, not that you are still thinking.
 - Every finished reply carries its cost: elapsed time and the context size at
   completion (`1m14s · 32K tok`) — a running total, not this turn's spend. IM
-  shows it as a footer line, the web on hover.
+  shows it as a footer line; the web shows the duration in the reply's activity
+  headline and the context size in the session header.
 - A reply past the platform's message cap is split across several messages
   (Telegram ~3.8k chars); the footer and the next-step buttons ride the last
   one.
@@ -96,16 +98,17 @@ operator's source of truth.
 
 ## Service restart, reload and update
 
-- `pier restart` is the graceful systemd path: it refuses new work, waits up to
-  five minutes for active turns and Task runs, then restarts. If the deadline
-  aborts an IM turn, the next process tells that conversation.
-- `pier reload` stays in-process: channel adapters re-read configuration and
-  idle, unwatched sessions reopen with current agent files on their next
-  message. Streaming or watched sessions are not interrupted.
-- `pier update` is deliberately different: the separate updater hard-stops the
-  service, backs up the database, replaces the package, and starts it again.
-  It can interrupt active work. All three are operator shell commands for an
-  installed Linux systemd service, not tools available to the agent.
+- `pier restart`: refuses new work, waits up to five minutes for active turns
+  and Task runs, then restarts. If the deadline aborts an IM turn, the next
+  process tells that conversation.
+- `pier reload`: channel adapters re-read configuration and idle, unwatched
+  sessions reopen with current agent files on their next message. Streaming or
+  watched sessions are not interrupted.
+- `pier update`: a separate updater backs up the database and installs the new
+  package while Pier is still up, then hard-stops and starts the service. From
+  the shell it does not drain, so it can interrupt active work; the Console's
+  Update and auto-update drain first. All three are operator shell commands for an installed Linux systemd
+  service, not tools available to the agent.
 
 ## Only the Console can change
 

package/skills/pier-slack/SKILL.md

@@ -30,8 +30,8 @@ Four things markdown cannot express:
   thread. Asking a human to paste their own user ID is never acceptable.
 - Escape `&` `<` `>` when they are text, not markup: `&amp;` `&lt;` `&gt;`.
 - Emoji as `:white_check_mark:`, not the raw glyph.
-- ~11,000 chars per message: split longer content across replies in one thread
-  rather than truncating.
+- 11,000 chars per message; the tool refuses longer `text`. Split longer
+  content across replies in one thread rather than truncating.
 
 ## Targeting
 

package/skills/pier-tasks/SKILL.md

@@ -25,6 +25,8 @@ status query. The receipt's `next` tells you where/how delivery happens:
   not for work you launch and forget. Receipt echoes `callbackMode`.
 - `callback:"none"`: no delivery; means you do not want the result, not pull later.
 - Single-run `callback_session_id`: deliver to another existing session.
+  Top-level sessions only, and never with `callback:"none"` or `tasks[]`;
+  inside a run it is refused, so your result always returns to you.
 
 Receipts include `runId`, `taskId`, state. Keep IDs: the callback also names
 `Run:`, and there is no lookup by task. `triggerSource` names the actual invoker
@@ -47,20 +49,21 @@ policy (`manual` means on demand).
 - Stored role: `run` with `task_id` and optional `input`;
   `session_mode:"fresh"` overrides a stored reuse policy. Archived tasks refuse.
 
-Use a `task` draft for `timeoutSeconds` or reuse:
+`timeoutSeconds` also works in the shorthand and in a `tasks[]` entry; use a
+`task` draft for reuse:
 
 ```json
-{"operation":"run","task":{"timeoutSeconds":3600,"action":{"type":"agent","session":{"mode":"reuse","sessionId":"..."},"prompt":"Check the result"}}}
+{"operation":"run","task":{"timeoutSeconds":7200,"action":{"type":"agent","session":{"mode":"reuse","sessionId":"..."},"prompt":"Check the result"}}}
 ```
 
-Inline drafts may omit `trigger`; only `manual` is allowed. Their nested
-`callback` is ignored: use top-level delivery options above. Nested callbacks
-matter for saved schedules (below).
+Inline drafts may omit `trigger`; only `manual` is allowed. A nested
+`callback` is refused: use the top-level delivery options above. Nested
+callbacks matter for saved schedules (below).
 
 ## Groups and chains
 
-`tasks[]` needs 2+ entries: prompt strings, `{prompt,cwd?,launch?,name?}`, full
-drafts, or `{task_id}`. Do not combine it with `task`, `task_id` or `session_mode`.
+`tasks[]` needs 2+ entries: prompt strings,
+`{prompt,cwd?,launch?,name?,timeoutSeconds?}`, full drafts, or `{task_id}`. Do not combine it with `task`, `task_id` or `session_mode`.
 
 ```json
 {"operation":"run","tasks":["Review correctness","Review test gaps"],"join":"all"}
@@ -93,13 +96,15 @@ available IDs by callback; invalid `launch.thinking` fails the call.
 
 ## Control and decisions
 
-`message` must be non-empty, <16 KiB. Controls require ownership: your delegated
+`message` must be non-empty, at most 16 KiB. Controls require ownership: your delegated
 trees, or only descendants when you are a subagent.
 
 - `steer`: interrupt a child with corrections.
 - `follow_up`: queue guidance after its current turn.
 - `resume`: terminal run only; same session, new run ID/callback, same depth,
-  message as prompt. Expires its unanswered decision.
+  message as prompt. Expires its unanswered decision. Being a new run, it takes
+  the same `callback` and `callback_session_id` as `run`, under the same rule:
+  a subagent may not redirect them.
 - `cancel`: run or group; cascades to descendants, terminal runs unchanged.
 
 `steer`/`follow_up` require a non-terminal run; undelivered guidance expires when
@@ -151,12 +156,15 @@ draft, including `trigger`. Schedules notify only with nested
 which scheduled runs lack.
 
 - Inside a run: Agent actions only (stored/inline), no reuse or create/update.
-- Depth 0–2: at most 3 runs below the invoking session; a fourth errors. Each
-  root allows 16 descendant runs (depth ≥1, resumes included). Your direct
+- Depth 0–2: three levels of nesting below the invoking session; a fourth
+  level errors. Each root allows 16 descendant runs (depth ≥1, resumes included). Your direct
   children are separate roots and do not count toward that limit.
-- 4 Agent runs execute instance-wide; others queue without error. Timeout
-  starts **at enqueue**, so a run can time out before starting.
-- Default timeout 900s; `timeoutSeconds:1–86400` in draft form only. Timeout
-  reports `failed / task timed out`.
+- 6 Agent runs execute instance-wide; others queue without error. A queued run
+  waits **unbounded**, ended only by cancellation or a restart.
+- Default timeout 3600s; `timeoutSeconds:1–86400` in a draft, the `prompt`
+  shorthand or a `tasks[]` entry. It starts when the run does, not at enqueue,
+  and reports `failed / task timed out`.
 - Restart marks queued/running runs `interrupted`; callbacks still apply.
   During drain, new roots are refused: retry after restart.
+- Watch probes that matched nothing are kept only 50 deep per watch; older
+  ones are deleted unless a message, a pending callback or a resume needs them.

package/dist/config-sync-fetch.js

@@ -1,84 +0,0 @@
-// Fetch one configuration document from the operator's source URL: HTTPS with
-// no credentials, redirects followed while they stay HTTPS, JSON capped at
-// 1 MiB so a hostile or broken source cannot exhaust memory.
-export const CONFIG_SYNC_BYTES = 1024 * 1024;
-const MAX_REDIRECTS = 5;
-export function configSourceUrl(raw) {
-    let url;
-    try {
-        url = new URL(raw.trim());
-    }
-    catch {
-        throw new Error("A valid HTTPS source URL is required");
-    }
-    if (url.protocol !== "https:" || url.username || url.password || url.hash || raw.length > 4096) {
-        throw new Error("Source must be HTTPS, without credentials or a fragment");
-    }
-    return url;
-}
-export async function downloadConfig(raw, etag, signal) {
-    let url = configSourceUrl(raw);
-    for (let hop = 0;; hop++) {
-        signal.throwIfAborted();
-        let res;
-        try {
-            res = await fetch(url, {
-                method: "GET", redirect: "manual", signal,
-                headers: { accept: "application/json", ...(etag ? { "if-none-match": etag } : {}) },
-            });
-        }
-        catch {
-            throw new Error(signal.aborted ? "Configuration download timed out or was cancelled" : "Could not connect to source");
-        }
-        const location = res.status >= 300 && res.status < 400 ? res.headers.get("location") : null;
-        if (location) {
-            await res.body?.cancel().catch(() => { });
-            if (hop >= MAX_REDIRECTS)
-                throw new Error("Source redirected too many times");
-            try {
-                url = configSourceUrl(new URL(location, url).href);
-            }
-            catch {
-                throw new Error("Source redirected to a location that is not HTTPS");
-            }
-            continue;
-        }
-        if (res.status !== 200 && res.status !== 304) {
-            await res.body?.cancel().catch(() => { });
-            throw new Error(res.status === 404 || res.status === 410
-                ? "Source link was revoked or does not exist"
-                : `Source returned HTTP ${String(res.status)}`);
-        }
-        const status = res.status === 304 ? 304 : 200;
-        if (status === 200 && !/^application\/json(?:\s*;|$)/i.test(res.headers.get("content-type") ?? "")) {
-            await res.body?.cancel().catch(() => { });
-            throw new Error("Source did not return JSON");
-        }
-        return { status, etag: res.headers.get("etag"), body: await read(res, signal) };
-    }
-}
-async function read(res, signal) {
-    const reader = res.body?.getReader();
-    if (!reader)
-        return "";
-    const chunks = [];
-    let size = 0;
-    try {
-        for (;;) {
-            const { done, value } = await reader.read();
-            if (done)
-                break;
-            size += value.length;
-            if (size > CONFIG_SYNC_BYTES)
-                throw new Error("Configuration exceeds 1 MiB");
-            chunks.push(Buffer.from(value));
-        }
-    }
-    catch (err) {
-        await reader.cancel().catch(() => { });
-        if (err instanceof Error && err.message === "Configuration exceeds 1 MiB")
-            throw err;
-        throw new Error(signal.aborted ? "Configuration download timed out or was cancelled" : "Configuration download failed");
-    }
-    return Buffer.concat(chunks).toString("utf8");
-}

package/dist/limits.js

@@ -1,14 +0,0 @@
-// The numbers more than one area has to agree on.
-//
-// Not policy or behaviour — a value several modules must spell the same way,
-// and a wrong copy makes two surfaces disagree about one session: a title
-// truncated to a different length depending on which path derived it.
-//
-// Here because a leaf may be imported by every area and depends on nothing
-// itself, which is the only shape that fits: agent/ derives a title and must
-// not import core/, web/ derives one too and must not import agent/, and the
-// browser needs the same numbers with no runtime behind them.
-/** How much of a message becomes a title, wherever one is derived: the listing
- *  reading a transcript (agent/listing.ts), a rename's fallback (agent/pi.ts),
- *  the fill at first prompt and the rename boundary (web/). */
-export const SESSION_TITLE_MAX = 80;