Code-local decisions

Decision headers: 367.

This is an inventory of decisions recorded in leading source-file headers. It is not an index of every issue mention: implementation comments, tests and fixture prose after the leading header are deliberately outside the inventory. Each qualifying file appears exactly once, with every issue cited by that header.

File	Issues	First complete decision sentence
packages/core/src/__tests__/config.test.ts	#59, #421	The config loading contract (#59, #421): a file that is there parses or fails CLOSED — every non-conforming input comes back unreadable, never as a silently-empty config — and no file is the defaults.
packages/core/src/__tests__/flow-trace.ts	#132, #482	A flow’s sequence as one test observed it (#482): the diagram on a docs/flows/ page is this recorder’s output, held by toMatchSnapshot, never drawn by hand.
packages/core/src/__tests__/git.test.ts	#453	#453: git read in a thread’s cwd, against real repositories built in a temporary directory — every baseline rule, the states a working tree can be in, and the settings that keep a read from writing or running anything the repository configures.
packages/core/src/__tests__/log-process.test.ts	#132	The file a user hands us (#132), end to end through the real configurator: what a line looks like, what never reaches it, what every line under a route carries — and the knob.
packages/core/src/__tests__/log-recorder.ts	#132, #178	The tests’ sink (#132), one for every package (#178): every enso record, at every level, into memory — a guard’s verdict, an audit line or a route’s problem is asserted as the record it is, the way a bundle reader would read it, not as a line on stderr.
packages/core/src/__tests__/log-stats.test.ts	#144	The day, derived (#144 slice 4): every number a fold over records that already exist, joined by the ids they carry and never by adjacency in a file three processes interleave.
packages/core/src/__tests__/log-tail.test.ts	#144	The reader’s question and the tail’s answer (#144 slice 2): what a filter admits, and what a poll over a growing, rotating file hands back.
packages/core/src/__tests__/no-duplicate-paths.test.ts	#59, #256	The anti-duplication anchor for path resolution (#59) — Daniel: “this should live in core and prevent duplicate code again.”
packages/core/src/__tests__/no-duplicate-shapes.test.ts	#255	Anchors for the reason this package exists: one place for every shape, reachable by one search.
packages/core/src/__tests__/observation-kinds.ts	#53	The oracle both “every observation” sweeps compare against (#53 S1.4): every kind literal the EnsoObservation union declares, sorted.
packages/core/src/__tests__/permission-rules.test.ts	#446, #496	#446, #496: the permission engine reads its policy from one path under the agent dir.
packages/core/src/__tests__/pi-manifest.test.ts	#221	pi’s manifest-resource layout, now owned in one place (#221 — it was implemented three times: the terminal launcher, the postinstall linker, and the server’s assertVendorLinks).
packages/core/src/__tests__/prompt-library.test.ts	#443	#443: a library prompt is a markdown file with a closed frontmatter block.
packages/core/src/__tests__/provider-refusal.test.ts	#340	A provider’s refusal, read the way pi’s providers write it (#340): the status pi puts in front, the class word a person glances at, and the provider’s own sentence out of its JSON.
packages/core/src/__tests__/run-context.test.ts	#435	#435: the run-context entry is a wire crossing — pi’s log holds whatever was appended — so a reader takes only the declared shape, and only under its own customType.
packages/core/src/__tests__/secrets.test.ts	#89	#89: secrets stay out of the environment the model’s tools inherit.
packages/core/src/__tests__/session-eval.test.ts	#441	#441: the session eval over fixtures.
packages/core/src/__tests__/thread-inspection.test.ts	#86, #100	The row formats are shared by the ?debug drawer and enso-thread.ts (PR #100 review: one definition, after the #86 pair had drifted).
packages/core/src/__tests__/thread-timeline.test.ts	#144	One thread, one ordering (#144 slice 3): the two tails and the log, by time, with the arrival order kept inside a tie and an unreadable stamp kept rather than dropped.
packages/core/src/ask-user.ts	#12	The agent’s ask_user tool (#12): what the model writes when it has a question only the user can answer.
packages/core/src/config.ts	#59, #421	Enso’s config (#59): the USER’s config.json in ENSO_HOME (~/.enso/config.json, #421).
packages/core/src/dialog.ts	#12, #27, #112	pi’s blocking extension dialogs, as data (#27, #112).
packages/core/src/follow.ts	#112	The server↔browser wire (#112): a thread’s feed, as the follow route serves it.
packages/core/src/git-state.ts	#453	What git says about a thread’s cwd (#453): the repository, the branch, what it pushes to, the commit the last push left on the remote, and the work that is not there yet.
packages/core/src/git.ts	#435, #452, #453	git, read (#453) — THE one way Enso runs git: the run-context recorder’s revision probe (#435) and the web server’s GET /api/threads/:threadId/git both come through {@link runGitIn}.
packages/core/src/log-bundle.ts	#132	The bundle (#132 item 5): ONE plaintext file a user attaches to an issue, built from things that already exist — the day’s records, the live threads’ inspections, the versions, and what the browser logged — with a manifest of what was redacted so the reader knows what is missing rather than wondering.
packages/core/src/log-process.ts	#132	A process’s sink (#132 item 2): ONE log for the harness — .enso/logs/enso-YYYY-MM-DD.jsonl, every process appending to the same day’s file, every record redacted by field name before it is written, and — for a terminal — a pretty console sink beside it at its own level.
packages/core/src/log-stats.ts	#132, #144	The day, derived (#144 slice 4): cost per thread and per model, how long each run took to its first token and to settle, how long each tool took, which guard rule refused what, and who wrote to today’s file — all of it from the records, none of it from a counter.
packages/core/src/log-tail.ts	#144	The reader’s question, and the tail’s answer (#144 slice 2).
packages/core/src/log.ts	#132	The harness’s log record (#132): one shape for every process, so a bundle a user hands us reads the same whichever layer wrote the line.
packages/core/src/paths.ts	#58, #59	The workspace path helpers (#59) — THE one place that walks the filesystem for roots.
packages/core/src/permission-mode.ts	#84, #162	The permission mode’s shape on the wire (#84; #162 workstream 4, L3): what a run starts in and what it may switch to.
packages/core/src/permission-modes.ts	#496, #499	Enso’s permission modes (#496): what each mode means, and how a session records which one it is in.
packages/core/src/permission-rules.ts	#446, #496	The permission policy pi runs under (#446, #496): ENSO_HOME/permissions.json, in @gotgenes/pi-permission-system’s format, never a copy of another tool’s settings.
packages/core/src/pi-manifest.ts	#211, #221	What a pi package’s manifest declares, and where pi will look for it (#221) — THE one place that knows pi’s manifest-resource layout.
packages/core/src/project.ts	#24, #395	Projects (#395): the local directories one Enso server runs threads in.
packages/core/src/prompt-library.ts	#443	The prompt library (#443): markdown files a person writes once and starts sessions with.
packages/core/src/provider-refusal.ts	#340, #384	A model provider refused a request (#340): the fact the page and the log were missing.
packages/core/src/run-context.ts	#126, #435, #436, #496	The run conditions pi does not record (#435, Lineage #126 receipt steps 3 and 5), and the fork point a thread’s manifest assembles from them.
packages/core/src/secrets.ts	#7, #89, #98	Secrets stay OUT of the environment the model’s tools inherit (#89).
packages/core/src/session-eval.ts	#381, #407, #441	A thread’s session eval (#441): a mechanical event timeline and a scorecard, computed from what the session recorded and nothing else.
packages/core/src/thread-context.ts	#361	One thread’s context, request by request (#361): what GET /api/threads/:threadId/context answers and the Context view draws — dsh-context’s composition and trend, over pi.
packages/core/src/thread-inspection.ts	#86	What a live thread’s session ACTUALLY contains, as the server reports it (#86).
packages/core/src/thread-runtime.ts	#69, #162, #165	The thread runtime: the contract the host implements for one thread, and the shapes that cross it (docs/glossary.md → Thread, Control).
packages/core/src/thread-stats.ts	#45, #359	One thread, analysed (#45 phase 2): what GET /api/threads/:threadId/stats answers and the chat’s stats drawer renders — per prompt, per turn, per tool.
packages/core/src/thread-timeline.ts	#132, #144	One thread, one ordering (#144 slice 3).
packages/core/src/tool-input.ts	#361	A tool call’s one-line subject — ls -la, src/x.ts, TODO — shared by the transcript’s step row (selected-message-part.tsx) and the Context view’s brief (host/branch-context.ts, #361), so a call reads the same in both.
packages/core/src/tool-result.ts	#16, #17, #18	The tool-result payload contract (#18), as a TypeBox schema.
packages/core/src/transcript.ts	#162	The transcript (#162 workstream 4, leak L2’s persistence side): a thread’s branch, root to leaf, as entries of OURS.
packages/core/src/web-fetch.ts	#9, #54, #59, #421	The web_fetch tool’s shapes and policy constants (#54).
packages/core/src/web-search.ts	#63	The web_search tool’s shapes and config section (#63).
packages/harness/core/__tests__/environment-dump.test.ts	#89	#89’s depth layer: the bash environment-dump deny.
packages/harness/core/__tests__/paths.test.ts	#53	⚠ FAIL CLOSED (#53 S3): no roots means nothing is inside — a misconfigured policy with an empty root list must deny, not allow, every write.
packages/harness/core/__tests__/project-trust.test.ts	#421	The replica of pi’s project-trust store (#421), held to pi’s OWN module.
packages/harness/core/__tests__/session-config.test.ts	#421	#421: the session’s config — the user’s, and over it a trusted project’s .enso/config.json.
packages/harness/core/__tests__/shell-fixtures.ts	#261, #289	Shell-shaped literals the scanner tests write, in one place (#261, PR #289 review).
packages/harness/core/__tests__/shell-secret-paths.test.ts	#204	The bash/powershell secret-path deny (#204).
packages/harness/core/__tests__/shell-segments.test.ts	#9, #89, #261	The tokenizer’s own contract (#261) — the parsing floor under the network deny (#9) and the environment-dump deny (#89), pinned directly instead of transitively.
packages/harness/core/__tests__/web-fetch-policy.test.ts	#54, #55	web_fetch’s pure policy (#54).
packages/harness/core/__tests__/web-search-model-providers.test.ts	#63	The google and openai providers (#63) against synthetic wire fixtures.
packages/harness/core/__tests__/web-search-support.test.ts	#63	The web_search support layer (#63): source hygiene, citation appliers, auth, Tavily.
packages/harness/core/__tests__/web-search-wire.test.ts	#63	The Anthropic WIRE (#63) against synthetic SSE fixtures — the wire serves both the anthropic and deepseek providers, so these fixtures are the shared spine.
packages/harness/core/deadline.ts	#58, #174	Run work under a deadline AND the caller’s abort signal, as one signal (#174; the shape web_fetch and web_search each carried).
packages/harness/core/environment-dump.ts	#89, #206	The bash environment-dump deny (#89) — DEPTH, not the fix.
packages/harness/core/index.ts	#173, #263	The harness’s own core — path resolution, guard state, and the web-search seam’s vocabulary.
packages/harness/core/network-egress.ts	#9, #54, #55, #57, #206	The bash network deny (#9) — a BAR, deliberately not a boundary.
packages/harness/core/project-trust.ts	#421	pi’s project-trust store, replicated (#421): the file, the lookup, the write and the lock.
packages/harness/core/read-tracker.ts	#10, #11, #57	Session-scoped record of files whose content this session has seen (#10), and of the on-disk state they had when it saw them (#11).
packages/harness/core/session-config.ts	#421	The config one session runs under (#421): the user’s ENSO_HOME/config.json, and over it the project’s own <cwd>/.enso/config.json — read ONLY once the project is trusted, by pi’s trust store and rules (project-trust.ts), so one answer covers the project’s .pi/ and .enso/.
packages/harness/core/shell-secret-paths.ts	#9, #89, #204	The bash/powershell secret-path deny (#204) — the read gate’s own policy, on the shell route.
packages/harness/core/shell-segments.ts	#9	Conservative shell command segmenter — the parsing floor under the bash network deny (#9).
packages/harness/core/tool-identity.ts	#4	Canonical tool identity (#4, gap 2).
packages/harness/core/web-fetch-policy.ts	#54, #55	web_fetch’s pure policy (#54) — every decision that needs no IO.
packages/harness/core/web-search/anthropic-wire.ts	#63	The Anthropic Messages WIRE — one streaming /messages call with the native web_search server tool, parsed into the outcome union.
packages/harness/core/web-search/auth.ts	#63	Model-routed auth (#63): resolve one model’s credentials THROUGH PI’s model registry — the same identity the conversation bills, including the OAuth path — with the provider-env fallback pi 0.80.1+ made necessary.
packages/harness/core/web-search/citations.ts	#63	Citation markers (#63): turn a provider’s citation records into [n] markers inside the answer text plus the numbered source list those markers point at.
packages/harness/core/web-search/dispatch.ts	#174	How every provider sends its request (#174): a JSON POST, and the two ways it fails — the request never left (requestDispatched: false, so the extension may fall through to the next provider) or the API answered but not OK (requestDispatched: true, the body quoted).
packages/harness/core/web-search/providers/anthropic.ts	#63	The anthropic provider (#63): current-model routing onto the Anthropic Messages native web_search server tool (ANTHROPIC_WEB_SEARCH_TOOL_TYPE in anthropic-wire.ts).
packages/harness/core/web-search/providers/deepseek.ts	#63	The deepseek provider (#63): the DEDICATED search backend, dsh’s shape (dsh-web-search-deepseek, MIT — the spec this follows).
packages/harness/core/web-search/providers/google.ts	#63	The google provider (#63): Gemini “Grounding with Google Search” over the streamGenerateContent SSE endpoint.
packages/harness/core/web-search/providers/openai.ts	#63	The openai provider (#63): the Responses API web_search tool, serving three model APIs — openai-responses, azure-openai-responses, and openai-codex-responses (including GitHub Copilot credentials, whose resolved endpoint rides the credential object).
packages/harness/core/web-search/providers/tavily.ts	#63	The tavily provider (#63): the FALLBACK — a dedicated retrieval API, not a model.
packages/harness/core/web-search/sources.ts	#63	Source hygiene for provider results (#63): URL normalization, junk filtering, and order-preserving dedupe.
packages/harness/core/web-search/sse.ts	#63, #268	A minimal SSE reader for the provider streams (#63).
packages/harness/core/web-search/vocabulary.ts	#56, #63	The web_search vocabulary (#63): provider ids, the outcome union, and the request shapes every provider module accepts.
packages/harness/core/web-search/wire-json.ts	#63, #64	Tiny helpers every provider wire shares (#63, PR #64 review): narrowing for unknown JSON wire payloads, and base-URL hygiene.
packages/harness/extensions/__tests__/tool-call-participants.test.ts	#4, #20, #62, #496	THE #4 TRIPWIRE — the arbiter trigger, made structural.
packages/harness/extensions/ask-user/__tests__/ask-user.test.ts	#12	The ask_user extension (#12) against a scripted UI: which way it asks on which surface, and what the plain-prompt path does with each answer — the path every surface can render, and the one a terminal user answers with the keyboard.
packages/harness/extensions/ask-user/index.ts	#12	The agent’s ask_user tool (#12): the model asks the user one to four questions, and the answers come back as the tool’s result.
packages/harness/extensions/guards/__tests__/cc-safety-net-contract.test.ts	#4, #9, #238	The cc-safety-net CONTRACT TEST (#9) — the condition #4’s comments set for adopting a vendor as a library: exact pin + a fixed command set asserted verdict-by-verdict, so a vendor bump that shifts the boundary goes red here instead of silently moving it.
packages/harness/extensions/guards/index.ts	#4, #9, #10, #11, #20, #21, #69, #496	Tier 0 guards — see docs/concepts/pi-immediate-needs.md.
packages/harness/extensions/logging/__tests__/logging.test.ts	#132	The extension’s two branches (#132): pi as a CHILD configures its own sink; pi IN-PROCESS leaves the server’s alone.
packages/harness/extensions/logging/index.ts	#132, #144, #167	The extension process’s logging (#132), and the one record only an extension can write: the provider’s own request id (#144).
packages/harness/extensions/permission-modes/__tests__/permission-modes.test.ts	#496	#496’s permission-modes extension through its factory: pi reduced to what the extension registers with and writes through, the engine’s service map and the classifier model faked.
packages/harness/extensions/permission-modes/index.ts	#441, #443, #496	Enso’s permission modes over the permission engine (#496).
packages/harness/extensions/run-context/__tests__/run-context.test.ts	#435, #438	#435’s recorder over its dependency seam (PR #438 review): the branches the review rounds added, each where a real run would take it — git and the config faked, pi reduced to the on it registers with and the appendEntry it writes through.
packages/harness/extensions/run-context/index.ts	#126, #435, #436, #438, #496	The run-context recorder (#435, Lineage #126): at every prompt’s run start, what the run starts under — git revision and dirty state, the resolved config’s hash and files, the skills, the context files’ hashes, the permission mode’s rule-set hash — appended to pi’s log as an enso-run-context entry (@enso/core run-context.ts) ONLY when a field differs from the last one on the branch.
packages/harness/extensions/system-prompt/__tests__/system-prompt.test.ts	#443	#443’s extension over pi’s surface reduced to what it touches — the on it registers with, the branch it reads, the notice it may give.
packages/harness/extensions/system-prompt/index.ts	#436, #443	A thread’s library system prompt, applied on EVERY surface (#443): at each prompt’s run start, the branch’s last enso-system-prompt entry is put into the run’s prompt options — a system prompt as pi’s custom preamble, an append prompt after whatever pi appends — so a thread started with a prompt in the web and resumed in the terminal (bun run enso, then /resume) runs the text it started with, not pi’s default.
packages/harness/extensions/web-fetch/__tests__/one-trust-question.test.ts	#421	#421, found live: the trust question for a project’s .enso/config.json must be asked ONCE per session, though two tools (web_fetch, web_search) read the config.
packages/harness/extensions/web-fetch/__tests__/web-fetch.test.ts	#54	The web_fetch extension (#54), against injected IO seams — no test here touches the network, DNS, or the user’s config file.
packages/harness/extensions/web-fetch/index.ts	#9, #54, #59, #421	The web_fetch tool (#54) — the sanctioned web access that replaces the ad-hoc network clients #9 denies in bash.
packages/harness/extensions/web-search/__tests__/web-search.test.ts	#63	The web_search extension (#63) against injected seams — the SELECTION and FALLBACK policy, and the ACCURATE rendering contract.
packages/harness/extensions/web-search/index.ts	#54, #63, #89, #132, #421	The web_search tool (#63) — provider-native search with a Tavily fallback, consumed from pi-web-search 1.4.0 (© ttttmr, MIT) and retyped behind enso’s seams.
packages/web/e2e/chat.e2e.ts	#27, #71, #486	The browser suite (#71, #486): drive the real chat surface in Chromium.
packages/web/e2e/e2e-home.ts	#486	The browser suite’s own ENSO_HOME (#486): a throwaway home the dev stack is started over, with threads already stored in it, so the suite has long transcripts to scroll and switch between with no model, and never reads or writes the operator’s real home.
packages/web/e2e/playwright.config.ts	#71, #486, #501	Playwright config for the browser suite (#71, #486).
packages/web/src/EnsoToolResult.tsx	#18	The web renderer for a enso tool result — the React half of #18’s contract.
packages/web/src/__tests__/browser-logging.test.ts	#132	The page’s logging (#132 slice 3): the ring the drawer reads, the shipper to the server, and the ?log= knob — driven through a real configure, asserted at the sinks.
packages/web/src/__tests__/chat-screen.test.tsx	#27, #49	#49, first pass: the dialog components had live receipts (#27, the e2e smoke) and no unit render, so chat-screen.tsx sat at ~14% lines.
packages/web/src/__tests__/command-palette.test.tsx	#338	⚠ A DOM before react-dom/client evaluates, and again if another mounting file has already released the one this module registered; dom-environment.ts has the measurement.
packages/web/src/__tests__/commands-connection.test.ts	#338	The palette’s read (#338): the route’s answer validated, a non-2xx said with its status and body, a payload the schema refuses said as such.
packages/web/src/__tests__/context-activity.test.tsx	#361	#361 phase 4: where Context Events and File Activity send the reader — an event to the first request it reached, an operation to its tool result in the request after its turn, and either to the next request when the branch has none that far yet.
packages/web/src/__tests__/context-browser.test.tsx	#361	#361 phase 3: the Context Browser, mounted — it reads the request it is asked for, and a focus (a brief’s line) opens that element’s category and picks its row, whose content the element view beside the list shows.
packages/web/src/__tests__/context-dialog.test.tsx	#361	#361 phase 5: /context’s dialog, mounted — it reads nothing while closed, and once open shows the composition and the browser, not the tab’s other cards (those stay on the Context tab).
packages/web/src/__tests__/context-trend.test.tsx	#361, #362	#361: the trend’s pick is the page’s — the Context Browser opens it and File Activity counts up to it — including when a change of granularity moves it to another request (#362 review).
packages/web/src/__tests__/custom-event-router.test.ts	#53, #90, #162	#53 S1.3: the CUSTOM-chunk router was an inline closure no test reached — renaming a chunk, dropping the notify-type allowlist, or swapping the two apply* calls all left the suite green.
packages/web/src/__tests__/diff-rows.test.ts	#452	#452: git’s unified diff, read the way git writes it, and laid out side by side the way a reader pairs an edit — each removed run beside the added run after it.
packages/web/src/__tests__/dom-environment.ts	#118	A browser DOM for the tests that MOUNT React (#118) — the mounted-pane tests, which need effects, useSyncExternalStore subscriptions and TanStack’s useChat to actually run.
packages/web/src/__tests__/file-tree.test.ts	#452	#452: the changed files as a tree — directories first, names sorted, totals per directory, and a chain of single-directory levels folded into one row.
packages/web/src/__tests__/fixture-conversation.test.ts	#27, #218	The compatibility probe that used to live in a PR body (#218).
packages/web/src/__tests__/follow-budget.test.ts	#272	The page’s follow budget (#272).
packages/web/src/__tests__/follow-connection.test.ts	#112	The adapter is the ONLY place AG-UI is made (#112).
packages/web/src/__tests__/fonts.test.ts	#407	#407 item 6: a font per role, kept in this browser, over the theme’s; and the families’ faces declared from their own stylesheets, unbundled.
packages/web/src/__tests__/fork-thread.test.ts	#433	#433: the fork route takes a pi entry id, and a prompt this page sent carries the id the composer minted, not its entry’s.
packages/web/src/__tests__/mode-lines.test.ts	#29, #90	#29’s remaining half: a mode change becomes a visible transcript line.
packages/web/src/__tests__/notifications.test.tsx	#29, #90	#29’s browser half: notify messages become visible transcript lines.
packages/web/src/__tests__/page-scoped-stores.test.ts	#103, #125	The anchor for #125 item 3 / #103 invariant 2 (switching threads leaks no state): every store that holds a THREAD’s state is created inside createThreadStores (thread-stores.ts), so a second thread on the page gets its own.
packages/web/src/__tests__/permission-mode.test.tsx	#84, #90	#84’s browser half: the CURRENT permission mode as state, and the control that changes it.
packages/web/src/__tests__/prompt-editor-state.test.ts	#443	#443: the prompt manager’s editor as data — what is unsaved, what may be saved, what a copy of pi’s default holds, and a rename’s order: the new file first, then the old one removed.
packages/web/src/__tests__/prompt-input.test.ts	#141	⚠ Upstream reported a refusal only when the WHOLE batch failed; a mixed drop lost files silently (PR #141 review).
packages/web/src/__tests__/prompt-library-connection.test.ts	#443	#443: the Start dialog’s library reads never throw — a failure is words the dialog shows beside the field, and pi’s default still starts.
packages/web/src/__tests__/questionnaire-card.test.tsx	#12	The ask_user card (#12), mounted: what it sends is what the server holds to the question and the tool reads back as the user’s words — one answer per question, in order — and it sends nothing until every question has one.
packages/web/src/__tests__/radix-preload.ts	#338	bun test preload (bunfig.toml): evaluate the modules that DECIDE BY document AT MODULE EVALUATION while a document exists, then take the document away again (#338).
packages/web/src/__tests__/scripted-server.ts	#112, #118	A scripted server behind fetch (#112, #118): one follow body the test writes SSE frames into, and unary routes the test scripts the answers of.
packages/web/src/__tests__/static-markup.ts	#236	What a <select> in a renderToStaticMarkup string offers, read through a DOM (#236).
packages/web/src/__tests__/stored-threads.test.ts	#103	#103 receipt, step 8: the dev proxy answered a dead API with Bun’s whole HTML error page, and quoting it filled the rail.
packages/web/src/__tests__/thread-changes.test.tsx	#452	#452: the Diff view as a static render — every state said as what it is, the tree, and the first file’s diff side by side.
packages/web/src/__tests__/thread-context.test.tsx	#361	#361: the Context view — its derivations as pure functions, and a static render of what it says it estimated, what the provider counted, and what it does not know.
packages/web/src/__tests__/thread-debug-drawer.test.tsx	#435, #440	The drawer, mounted, reading its fork point (#435).
packages/web/src/__tests__/thread-debug.test.tsx	#86	#86: the drawer’s one job is to NAME a disagreement between what the browser believes and what pi’s session holds.
packages/web/src/__tests__/thread-eval.test.tsx	#441	#441’s Stats-tab panel: a static render of what the eval says it counted, what it could not, and the timeline’s two counters — never a verdict.
packages/web/src/__tests__/thread-git.test.tsx	#453	#453: the status bar’s git readout — the pure view in every state git can be in, the read of its route in every way it can go, and the count whose change asks again.
packages/web/src/__tests__/thread-stats.test.tsx	#45	#45 phase 2: the stats drawer, livecraft’s session analysis over our wire — its derivations as pure functions, and a static render of what it says it measured and what it could not.
packages/web/src/__tests__/thread-status.test.tsx	#45, #90	#90 PR 1: the always-on status bar.
packages/web/src/__tests__/thread-url.test.ts	#142	The URL is the source of truth for the active thread (#142): what it names, and what it cannot.
packages/web/src/__tests__/threads-rail.test.tsx	#90	#90 PR 3: the sessions rail and the page’s thread list behind it.
packages/web/src/__tests__/transcript-reveal.test.ts	#359	#359: a stats target → the transcript row it names.
packages/web/src/add-project.tsx	#395	Add a project (#395 slice 3): browse the directories the install allows — inside the roots the user’s config declares (ENSO_HOME/config.json) — and register one.
packages/web/src/browser-logging.ts	#86, #132	The browser’s logging (#132 slice 3).
packages/web/src/command-palette.tsx	#31, #338, #341, #343, #361, #390	The / command palette (#338, slice 1): Claude Code’s / button in VS Code, as a popup over the composer — a filter box, rows grouped by where the command came from, a description on each row.
packages/web/src/commands-connection.ts	#144, #338, #344	The / palette’s one read (#338, slice 1): GET /api/threads/:id/commands — the slash commands the thread’s session registers, grouped by the server into extension commands, prompt templates and skills, with a source that says whose list it is (live: this thread’s session; remembered: the last built session’s, because every session builds it from the same sources under the same configuration and this thread has no live session — never ran, or ran and idled out; the server cannot tell; none: no session has been built in this process).
packages/web/src/context-activity.tsx	#361	The Context view’s side cards (#361 phase 4), in the design direction’s row language — dsh-context’s Context Events (when and why the window changed) and File Activity (what pi’s file tools did, up to the trend’s picked request).
packages/web/src/context-browser.tsx	#361	The Context Browser (#361 phase 3) — dsh-context’s “open the box of any request”, in the design direction’s two columns: pick the next request or any past one (the picker, or a step either way), and see what it was assembled from — six categories, each expanding into one row per element with its estimate — beside the element picked: a prompt section, a tool’s schema, a message, a reply’s parts, a tool result beside its call’s arguments.
packages/web/src/context-labels.tsx	#443	The thread’s system prompt, for the Context view’s labels (#443): a custom prompt is visible in the evidence — the system-prompt row says which prompt it is, and the section the prompt wrote says so — not only in the dialog that chose it.
packages/web/src/context-parts.tsx	#361	The Context view’s shared pieces (#361): its number formats, and the six-category bar and legend — drawn by the Now card and the Context Browser alike.
packages/web/src/custom-event-router.ts	#103	The one chunk that is neither an observation nor a frame: the follow ended without this page leaving it (#103 receipt) — the server closed, restarted, or dropped the connection.
packages/web/src/debug/__tests__/log-tail-connection.test.ts	#144	The log tail client (#144 slice 2), driven over a scripted body: SSE text the test writes, read as the page reads it.
packages/web/src/debug/__tests__/log-tail-screen.test.tsx	#118	⚠ Loaded by a DYNAMIC import, and that is the one place this repo needs one: react-dom/client probes the DOM when its module evaluates ("oninput" in document), and bun evaluates node_modules imports before a local side-effect import can register happy-dom — statically imported it sits in an IE-era polyfill mode where onChange never fires.
packages/web/src/debug/day-stats-screen.tsx	#31, #144	The day’s stats and the processes view (#144 slice 4): what today cost, per thread and per model; how long each run waited for its first token and for the prompt to settle; how long each tool took; which guard rule refused what; who has written to today’s file; and which threads the server holds live right now — on the debug page at debug.html?stats.
packages/web/src/debug/debug-screen.tsx	#144	The debug page, by its URL (#144 slices 3–4): debug.html is the day’s tail, debug.html?thread=<id> is that thread’s timeline, and debug.html?stats is the day’s stats and processes view.
packages/web/src/debug/log-row.tsx	#144	One log record, one rendering (#144 slice 3) — shared by the day’s tail and a thread’s timeline, so a record reads IDENTICALLY on both pages and a reader who follows a thread id from the tail into the timeline finds the same row, not a second dialect of it.
packages/web/src/debug/log-tail-connection.ts	#144, #336	The browser’s connection to GET /api/logs/tail (#144 slice 2): the day’s file, filtered by the server, arriving as SSE frames.
packages/web/src/debug/log-tail-screen.tsx	#144	The debug log page (#144 slice 2): the day’s records, as the file has them, in a browser.
packages/web/src/debug/log-tail-view.tsx	#352	What the two tail-fed pages — the day’s log (log-tail-screen.tsx) and one thread’s timeline (thread-timeline-screen.tsx) — share, held once (#352): the view the frames build, the hook that keeps one tail open and resumable, and the pinned, virtualized list both render into.
packages/web/src/debug/thread-timeline-screen.tsx	#144	One thread’s timeline (#144 slice 3): what the host emitted, what the server sent, and what was logged, as ONE list ordered by time — on the debug page at debug.html?thread=<id>.
packages/web/src/diff-rows.ts	#452	A unified diff as the Diff view draws it (#452): git’s patch for one file, parsed into hunks, and each hunk laid out side by side — the old file on the left, the new on the right.
packages/web/src/file-tree.ts	#452	The Diff view’s file tree (#452): the changed files, by directory, the way a reader scans a change — directories first, then files, each sorted by name, and each directory carrying the lines added and removed under it.
packages/web/src/fixture-conversation.ts	#27, #31, #75, #404	The styling dev loop (#31): a scripted conversation streamed through the REAL useChat pipeline as local AG-UI events — no server, no pi.
packages/web/src/follow-connection.ts	#112, #272, #274	The browser’s connection to a thread (#112): TanStack’s SubscribeConnectionAdapter over the prompt/follow split.
packages/web/src/fonts.ts	#407	The page’s fonts (#407 item 6): the families it ships, the per-role choice in Settings, and how both reach the page.
packages/web/src/fork-thread.ts	#433	Forking from the page (#433): a user message’s fork action and the palette’s /fork both land here, and the page opens what the fork route answers.
packages/web/src/guard-refusal.tsx	#387, #407	A guard refusal as the design draws it (Enso-Design-Direction .guard, #407 item 1): the tool, the verdict in the refusal colour, what was asked, why it was refused, and who refused it.
packages/web/src/host/__tests__/agent-host.test.ts	#27, #45, #69	The in-process host against the REAL harness package (#69) — every extension the manifest names loads, and inline probe extensions observe what the host does.
packages/web/src/host/__tests__/agent-loop-contract.test.ts	#130	A CONTRACT TEST on the runtime’s loop, the shape of cc-safety-net-contract.test.ts: the wire shape of a refused tool call is the vendor’s doing — a guard’s { block, reason } becomes an error result with the reason as its content, isError: true — and map-events.ts relies on it (the tool_execution_end case, “isError is the only signal a refused call has”).
packages/web/src/host/__tests__/branch-context.test.ts	#361	#361: a thread’s context, request by request, off pi’s own entries — built here with pi’s real session manager, so the entries read are the ones pi writes and the assembly is pi’s own (buildContextEntries, compaction included).
packages/web/src/host/__tests__/branch-stats.test.ts	#45	#45 phase 2: the branch, analysed off pi’s own entries — built here with pi’s real session manager, so the shapes read are the ones pi writes.
packages/web/src/host/__tests__/context-history.test.ts	#361	#361 phase 4: Context Events and File Activity, off pi’s own entries — built with pi’s real session manager, so every entry kind is one pi writes.
packages/web/src/host/__tests__/continuation.test.ts	#436	continuationLead (#436): whether a torn thread can be continued from its stored state, and what closes it first.
packages/web/src/host/__tests__/event-tail.test.ts	#97	#97’s tail is a debugging surface: what it must not do is lie by omission.
packages/web/src/host/__tests__/extension-ui-context.test.ts	#69	The ExtensionUIContext the host binds (#69), driven directly: the blocking methods become extension_ui_request records and resolve on an answer, a cancel, an abort signal or a timeout; the fire-and-forget methods emit and return; the terminal-only surface is inert — pi’s rpc mode’s behaviour, which extensions already tolerate.
packages/web/src/host/__tests__/host-flows.test.ts	#338	The flow decisions (#338 slice 3), as the fake and the real host share them: what /login and /logout offer, what a run must name, and the words the flow says.
packages/web/src/host/__tests__/notice-sender.test.ts	#387	#387 gap 2: who said a notice.
packages/web/src/host/__tests__/project-trust.test.ts	#502	#502: the host’s trust decision, against real directories and pi’s real trust.json store.
packages/web/src/host/__tests__/session-events.test.ts	#69	The replica of pi’s unexported toJsonEvent (#69): what map-events.ts consumes must be byte-for-byte the rpc wire shape.
packages/web/src/host/__tests__/session-usage.test.ts	#45	#45: which session events make the host re-read pi’s totals.
packages/web/src/host/__tests__/stored-session.ts	#95, #486	A stored thread, written the way pi writes one (#95, #486): a session created under the thread’s id and whole turns appended, each a user message and pi’s reply.
packages/web/src/host/__tests__/system-prompt-preview.test.ts	#443	#443: the preview splits pi’s rendering — the preamble, then each section inside its tags, joined by blank lines — and refuses a rendering that does not fit what the host knows of it.
packages/web/src/host/branch-context.ts	#361	A thread’s context, request by request (#361) — the host half of EnsoThreadContext and of EnsoContextRequestDetail, read off pi’s own entries for a live session and a stored file alike.
packages/web/src/host/branch-eval.ts	#441	The branch as the session eval reads it (#441): the transcript as ours (leak L2) and the turns’ usage from the same walk the stats drawer uses.
packages/web/src/host/branch-stats.ts	#45, #359	A thread’s branch, analysed (#45 phase 2): per prompt, per turn, per tool — the session half of EnsoThreadStats.
packages/web/src/host/context-elements.ts	#361, #443	A request’s context as ELEMENTS (#361) — dsh-context’s browser rows: a prompt section, a tool definition, a message, a tool result — and the prices the makeup sums, so the trend’s bars and the browser’s rows are one computation, not two that could drift.
packages/web/src/host/context-history.ts	#361	What happened to a thread’s context, and to its files (#361 phase 4) — dsh-context’s Context Events and File Activity, read off pi’s own entries along the branch.
packages/web/src/host/continuation.ts	#436	What a Continue sends ahead of the model’s next request (#436): the decision whether a torn thread can be continued from exactly its stored state, and what closes it first.
packages/web/src/host/event-tail.ts	#69, #84, #86, #88, #97	A thread’s event tail (#97): the last N events through one funnel, with provenance.
packages/web/src/host/fork-point.ts	#433, #434, #435, #443	A thread’s fork point (#435), assembled from its branch alone — the same walk for a live session’s memory and a stored file, so the manifest of a thread reads one way whether it is running.
packages/web/src/host/host-commands.ts	#338, #341	The host command source (#338 slice 2) — the rows the host appends to listCommands() and the decision behind runHostCommand, as PURE functions over a model state and a model list.
packages/web/src/host/host-flows.ts	#338	The flow host commands (#338 slice 3): /login and /logout, as PURE decisions over what the model runtime reports — the rows the host appends to listCommands(), the check a run passes before anything starts, and the sentences the flow says as it goes.
packages/web/src/host/map-events.ts	#24	pi rpc events → the observations a surface renders (#24).
packages/web/src/host/notice-sender.ts	#387	Who said a notice (#387 gap 2).
packages/web/src/host/permission-mode-adapter.ts	#84, #162, #496	The permission mode, as the host reads and sets it (#84, #496; below the seam since #162 workstream 4, L3).
packages/web/src/host/project-trust.ts	#502	Whether a hosted session may read its project’s own configuration (#502): decided HERE, before pi builds anything.
packages/web/src/host/questionnaire-dialog.ts	#12	The agent’s ask_user questionnaire, lifted to a dialog the web card asks as one (#12).
packages/web/src/host/runtime-event.ts	#69, #162	The runtime’s event, as the host receives it — BELOW the thread-runtime seam since #162 workstream 4 (L2).
packages/web/src/host/session-events.ts	#69	AgentSessionEvent → the rpc WIRE shape (#69).
packages/web/src/host/session-usage.ts	#45, #86	A thread’s spend and context, as pi reckons them (#45) — the two halves of EnsoSessionUsage.
packages/web/src/host/system-prompt-preview.ts	#443	A system prompt before it is sent (#443): what a thread’s next request would carry with a given library prompt — or pi’s default — section by section, priced as the Context tab prices it.
packages/web/src/host/system-prompt.ts	#390, #443	A session’s system prompt from the library (#443), handed to pi through pi’s OWN mechanism.
packages/web/src/host/transcript.ts	#162, #434	The runtime’s session branch → the transcript of ours (#162 workstream 4, L2’s persistence side).
packages/web/src/listing-store.ts	#29, #86, #95, #395	A list the server hands the page and the rail shows — stored threads (#95), projects (#395).
packages/web/src/markdown-image.tsx	#350	⚠ A MARKDOWN IMAGE IS A FETCH, so a remote one waits for a click (PR #350 review).
packages/web/src/mode-lines.ts	#29, #69, #88, #162	Permission-mode lines in the transcript (#29, the remaining half).
packages/web/src/model-state.tsx	#44, #90, #338, #341, #434	The model the thread runs and how hard it thinks, as STATE — and the two composer controls that change them (#338 slice 2; the control half of #44).
packages/web/src/notifications.tsx	#29, #84, #94, #96	pi’s notify messages, rendered (#29).
packages/web/src/option-select.tsx	#45	A closed vocabulary as a control (#45 phase 2 folded the log level’s and the stats drawer’s copies): a native <select> — keyboard- and screen-reader-complete without a dependency, the reasoning the permission-mode control gives — that only ever hands back one of its options.
packages/web/src/page-clock.ts	#278	The page’s clock as a store (#278): the one value that changes with no input.
packages/web/src/permission-mode.tsx	#73, #84, #90	The CURRENT permission mode, as state — and the control that changes it (#84).
packages/web/src/project-list.ts	#395	The projects the rail groups threads under (#395): the launch directory first, then the ones registered under the install’s roots, as GET /api/projects lists them.
packages/web/src/prompt-editor-state.ts	#443	The prompt manager’s editor, as data (#443): the draft on screen, the file it was opened from, and the rules a save follows — kept apart from the React so each is tested as the value it is.
packages/web/src/prompt-library-connection.ts	#443	The prompt library’s reads (#443): GET /api/prompts and GET /api/prompts/:id, validated with the wire’s own schemas, as commands-connection.ts reads the palette’s list.
packages/web/src/prompt-manager.tsx	#443	The prompt manager (#443): one place to read, write and organise the prompts a session runs with — the header’s scroll button, beside Settings, because the library is the user’s, not a thread’s.
packages/web/src/prompt-size.tsx	#443	What a prompt costs, always in view while it is written (#443): the file’s bytes, exact; the body’s tokens, ≈ — estimateTextTokens, the function the Context tab prices system text with — and, once pi has rendered it, its share of the model’s window.
packages/web/src/questionnaire-card.tsx	#12	The agent’s ask_user questionnaire as one card (#12): a tab per question, each option a row with its label and what choosing it means, an “Other” row for an answer in the user’s own words, and one “Submit answers” once every question has one.
packages/web/src/read-on-usage.ts	#45, #361, #362, #404, #453	A thread’s route, read on mount and again whenever the thread’s usage moves (#45, #361) — the Stats and Context views’ one refresh rule.
packages/web/src/refused-attempt.tsx	#387	Who refused, as a reader names them (#387): pi’s display name for the provider (Anthropic), else its id; undefined when the refusal names no provider.
packages/web/src/route-read.ts	#45	One GET of a JSON route whose answer has a schema, in the three ways it can go — a failure is words, never a throw (#45 phase 2 folded the thread timeline’s and the stats drawer’s copies).
packages/web/src/server/__tests__/bun-plugin-strict-binding-workaround.test.ts	#237	The dev bundle’s one source rewrite, executed (#237).
packages/web/src/server/__tests__/dev-proxy.test.ts	#160	#160: the web surface (5178) forwards /api/* to the Enso server (5179), whose admission check refuses a request from a non-loopback page.
packages/web/src/server/__tests__/fake-hosted-thread.ts	#178	The one fake of the thread-runtime seam (#178; docs/seams/thread-runtime.md): a ThreadRuntime from plain closures that records every call, so the server, the registry and the routes are driven over it and asserted through what it recorded.
packages/web/src/server/__tests__/follow-reader.test.ts	#231	The double’s own contract (#231).
packages/web/src/server/__tests__/follow-reader.ts	#231	A follow as a test reads it: frames and keepalive comments as they arrive, awaited by count — never by a guessed delay.
packages/web/src/server/__tests__/follow.test.ts	#109, #112	The wire, measured (#109’s receipt, kept as the contract — #112).
packages/web/src/server/__tests__/font-files.test.ts	#407	#407 item 6: the page’s fonts are served unbundled from the installed @fontsource packages.
packages/web/src/server/__tests__/live-or-stored.test.ts	#45, #361	The analysis routes’ one read rule (#45, #361), the rule thread-read.ts reads by: peek, read the file if not live, re-peek.
packages/web/src/server/__tests__/logs-route.test.ts	#132	POST /api/logs (#132 slice 3): the browser’s batch into this process’s logger, under the browser’s own category, at its level, marked as the browser’s — or a 4xx that is never a record of its own.
packages/web/src/server/__tests__/logs-stats-route.test.ts	#144, #336	The stats route’s own three facts (#144 slice 4, PR #336 review): WHICH file it folds is the clock’s local day, a day nobody has written is an empty answer and not a failure, and a line that is not a record is counted rather than folded.
packages/web/src/server/__tests__/logs-tail-route.test.ts	#97, #144	GET /api/logs/tail (#144 slice 2), over real HTTP: the day’s file, filtered server-side, as frames the browser’s schema takes — and NO record of its own, which is the rule the whole debug surface rests on (#144, #97).
packages/web/src/server/__tests__/observation-log.test.ts	#144	The tier an observation lands at, and the one record that is not an observation at all: the run’s time to first token (#144).
packages/web/src/server/__tests__/projects.test.ts	#395	The project boundary (#395), decided in projects.ts: which directories a page may make projects of, and where a new thread is built.
packages/web/src/server/__tests__/run-timing.test.ts	#144	Time to first token, once per run (#144).
packages/web/src/server/__tests__/server-handler.test.ts	#76, #86, #95, #97	The server’s routes beside the wire, over real HTTP (#76, #86, #95, #97): what the inspection, history and session-listing routes report about threads the prompt route built.
packages/web/src/server/__tests__/thread-context-route.test.ts	#361	#361: one thread’s context — pi’s branch and pi’s meter, from memory for a live thread and from the file otherwise, building nothing to answer.
packages/web/src/server/__tests__/thread-eval-route.test.ts	#441	#441: one thread’s eval — the branch from pi, the log’s queued admissions and aborts from the day files the branch spans.
packages/web/src/server/__tests__/thread-git-route.test.ts	#452, #453	#453: one thread’s git state — asked in the live thread’s cwd, or the stored thread’s, building nothing to answer, and never in a directory the server does not serve.
packages/web/src/server/__tests__/thread-stats-route.test.ts	#45	#45 phase 2: one thread’s stats — pi’s session for the numbers, the day files for the times.
packages/web/src/server/__tests__/transcript-to-messages.test.ts	#95, #162	#95: a stored branch mounts as the messages a live run would have left behind.
packages/web/src/server/__tests__/vendor-links.test.ts	#160	⚠ The precondition that was missing when a real run failed.
packages/web/src/server/bundle-route.ts	#132, #137	GET /api/logs/bundle[?thread=<id or prefix>] (#132 item 5): the day’s records, the live threads’ inspections, and the versions, as ONE markdown file with the records fenced as JSONL — bun run logs --file reads it back.
packages/web/src/server/dev-proxy.ts	#34, #38, #160	The web surface’s /api/* hop to the Enso server (dev-web.ts), streaming both directions.
packages/web/src/server/dev-web.ts	#9, #36	Dev entry point for the web surface — Bun’s fullstack dev server, replacing vite (#36).
packages/web/src/server/dev.ts	#9, #132, #395, #421	Dev entry point for the enso server.
packages/web/src/server/follow.ts	#75, #109, #112, #116, #162, #436	The prompt/follow split (#112) — the server↔browser wire.
packages/web/src/server/font-files.ts	#407	The page’s fonts, served as files rather than bundled (#407 item 6).
packages/web/src/server/live-or-stored.ts	#45, #86, #361	A thread’s answer from pi’s memory when it is live, from its file when it is not (#45, #361) — READ THE WAY thread-read.ts READS: peek, read the file if not live, re-peek.
packages/web/src/server/logs-route.ts	#132	POST /api/logs (#132 slice 3): the browser’s records, into the one file.
packages/web/src/server/logs-stats-route.ts	#97, #144	GET /api/logs/stats (#144 slice 4): the day, derived — dayStats over today’s file, as JSON, for the debug page’s stats view.
packages/web/src/server/logs-tail-route.ts	#97, #132, #144	GET /api/logs/tail (#144 slice 2): the day’s file, filtered server-side, as SSE — what the debug page reads instead of a terminal.
packages/web/src/server/observation-log.ts	#97, #132	Every observation the server publishes becomes a record (#132, “trace everything”) — at the tier it belongs to, with the ids that join it to the transcript, the event tail (#97) and the other layers’ lines about the same moment.
packages/web/src/server/projects.ts	#24, #395, #399	The projects one server runs threads in (#395).
packages/web/src/server/prompt-library.ts	#443	The prompt library on disk (#443): ENSO_HOME/prompts/<id>.md, read on every request — the files are the record, so an edit made in another editor is what the next list shows.
packages/web/src/server/run-timing.ts	#144, #160	When a run was admitted, so its FIRST delta can be recorded as a latency (#144 slice 1).
packages/web/src/server/sse.ts	#109	The SSE plumbing every streaming route shares: the response headers and the keepalive.
packages/web/src/server/thread-context-route.ts	#86, #361	GET /api/threads/:threadId/context (#361): the thread’s context, request by request — the Context view reads it.
packages/web/src/server/thread-eval-route.ts	#441	GET /api/threads/:threadId/eval (#441): one thread’s session eval — the mechanical timeline and scorecard session-eval.ts computes.
packages/web/src/server/thread-git-route.ts	#86, #452, #453	GET /api/threads/:threadId/git (#453): git’s state in the thread’s cwd — the repository, the branch, the last-push baseline and the work not yet pushed (@enso/core/git).
packages/web/src/server/thread-log-days.ts	#45, #441	A thread’s records in the day files (#45, #441): which days are on disk, which local day a moment falls on, and one day’s lines for one thread.
packages/web/src/server/thread-manifest-route.ts	#86, #435	GET /api/threads/:threadId/manifest (#435): the thread’s fork point — its identity, then the conditions it runs under (recorded model and level, mode, cwd, the latest enso-run-context) — off the branch the host walks (host/fork-point.ts).
packages/web/src/server/thread-read.ts	#214	THE LIVE-OR-COLD READ, ONCE (#214).
packages/web/src/server/thread-registry.ts	#43, #69, #113, #116	One pi session per chat THREAD, held across runs (#69 PR 2 — closes #43).
packages/web/src/server/thread-stats-route.ts	#45, #358, #359	GET /api/threads/:threadId/stats (#45 phase 2): one thread, analysed — the chat’s stats drawer reads it.
packages/web/src/server/transcript-to-messages.ts	#93, #95, #162, #220	The transcript → TanStack UIMessages (#95): the history a resumed thread mounts with.
packages/web/src/settings-dialog.tsx	#407	The page’s settings (the header’s gear): its colour theme, and a font per role (#407).
packages/web/src/start-session-prompts.tsx	#443	The Start dialog’s two library fields (#443): the session’s system prompt — pi’s default, or a system / append prompt, fixed for the session’s life — and a saved session prompt that fills the first message.
packages/web/src/start-session.tsx	#390, #391, #443	The Start-a-session dialog (#391): a new thread opens on it — the model, the effort, the mode, the system prompt (#443, pi’s default or one from the library) and the first prompt, then Start session.
packages/web/src/stats-table.tsx	#45, #144	The table and the number formats the two stats surfaces share (#45 phase 2): the day’s (debug/day-stats-screen.tsx, #144) and one thread’s (thread-stats.tsx).
packages/web/src/store.ts	#90	The smallest external store React can subscribe to: one value, replaced whole, and a listener set.
packages/web/src/stored-threads.ts	#95, #395	The sessions a user can come back to (#95): pi’s session files in this server’s projects, as the server lists them — the rail’s rows under each project (#395).
packages/web/src/thread-changes.tsx	#452, #453	The Diff view (#452): every file in the thread’s project that differs from the last push, as a tree, and the chosen file’s diff side by side — the old file on the left, the new on the right.
packages/web/src/thread-context-analysis.ts	#361	What the Context view derives from EnsoThreadContext before it draws (#361): the category order and names, totals, the prompt-granularity roll-up and the delta series — dsh-context’s categories.ts, headline.ts and trend aggregation, over our wire.
packages/web/src/thread-context.tsx	#361	The Context view (#361) — dsh-context’s Context tab over pi, in the design direction’s layout (Enso-Design-Direction, the Context view): Now (what the next request is made of, beside the provider’s count for the last one), Trend (every request’s makeup, and the picked one’s brief), then the Context Browser with Context Events and File Activity beside it on a wide view.
packages/web/src/thread-eval.tsx	#441	The session eval on the Stats tab (#441, the follow-up its issue named): the scorecard, the agent-side signals and the timeline GET /api/threads/:threadId/eval answers, under the stats drawer.
packages/web/src/thread-git.tsx	#453	The status bar’s git readout (#453): the branch, how far it is ahead of and behind the last push, and the work in the tree — off GET /api/threads/:threadId/git, whose tooltip names the baseline and the rule that chose it (@enso/core git-state.ts).
packages/web/src/thread-stats-analysis.ts	#45, #387, #407	What the stats drawer derives from EnsoThreadStats before it draws (#45 phase 2): the averages, the per-tool totals and the two rankings — pi-livecraft’s analyzeSession and SessionAnalysisWidget rankings (.inspiration/pi-extensions/pi-livecraft), ported to our wire.
packages/web/src/thread-stats.tsx	#45, #359	The thread’s stats drawer (#45 phase 2) — pi-livecraft’s session analysis widget (.inspiration/pi-extensions/pi-livecraft/src/features/session-analysis/), section for section, over our wire: summary cards, context and tokens per turn, cost per turn, cumulative usage by tool, costliest calls, distribution, costliest prompts.
packages/web/src/thread-status.tsx	#45, #51, #84, #90, #103	The status bar (#90 PR 1): the always-on line that says what this session is doing and what it has cost, so the answer to “is anything happening?”
packages/web/src/thread-stores.ts	#90, #272	Everything the browser knows about one thread beyond its messages (#90 PR 3).
packages/web/src/thread-url.ts	#95, #142	The thread a page URL names (#142): ?thread=<id>.
packages/web/src/threads-rail.tsx	#90, #95, #104, #114, #278, #395, #433	The threads rail (#90 PR 3, #395): which conversation am I in, in which project, what else is there, how do I start another.
packages/web/src/to-agui.ts	#18, #24, #112	EnsoObservation → AG-UI StreamChunk (#24, #112).
packages/web/src/transcript-reveal.ts	#359, #360	From a point or a row in the stats drawer to the transcript row it describes (#359) — pi-livecraft’s onNavigate({ kind: 'turn' | 'message' | 'tool' }), over our transcript.
packages/web/src/view-parts.tsx	#361	The analysis views’ building blocks — the Context and Stats tabs (#361), in the design direction’s card language (Enso-Design-Direction, .card, .seg, .filter, .kind): a card with a head (title, a muted line saying how to read it, its controls on the right) over its body, a segmented choice, a small button, a filter pill and a row’s kind label.
scripts/__tests__/enso-eval.test.ts	#441	bun run eval (#441): the flags, and the three renderings over one payload — the markdown’s running counters, the row that a header names column for column, the comparison table.
scripts/__tests__/enso-launch.test.ts	#221	The terminal launcher’s decisions (docs/flows/boot-and-launchers.md).
scripts/__tests__/enso-logs.test.ts	#132	The reader’s own logic (#132, bun run logs): the flags, and what a line must be to print.
scripts/__tests__/pi-version-parity.test.ts	#69, #217	THE TWO PI RESOLUTIONS, HELD TOGETHER (#217).
scripts/check-coverage.ts	#49, #118, #234	The TOTAL coverage floor — the gate that bunfig.toml cannot express.
scripts/docs/build-docs.ts	#482	Builds every docs page that is BUILD OUTPUT (#482): the reference pages each generator prints and the flow pages flow-pages.ts assembles.
scripts/docs/core-exports.ts	#170	Generates docs/reference/core-exports.md (#170): the public core barrel and the node-only logging subpath, with their defining declarations and production importers.
scripts/docs/decisions.ts	#170	Generates docs/reference/decisions.md (#170): one row for each owned source file whose first comment/header block cites an issue.
scripts/docs/env-and-config.ts	#170	Generates docs/reference/env-and-config.md (#170): the explicit environment boundary, the composed EnsoConfig shape, every .enso/ path assembled by core, and the harness manifest resources.
scripts/docs/extract-declaration.ts	#168	The docs gate’s one primitive (#168): a top-level declaration, by name, whole.
scripts/docs/feature-model.ts	#437	A stand-in for Anthropic’s Messages API that plays a scripted conversation (#437).
scripts/docs/feature-pages.ts	#482	Builds docs/features/<id>.md for every feature spec (#482): BUILD OUTPUT, gitignored, written by bun run docs:build and the site build.
scripts/docs/feature-screenshots.ts	#404, #437, #482	Captures the Features screenshots (#437) into docs/features/images/.
scripts/docs/feature-session.ts	#437	The session the Features screenshots are taken from (#437): a small project, four prompts, and what the model answers to each.
scripts/docs/features/index.ts	#482	Every Features page, each built from its spec (#482).
scripts/docs/features/landing.ts	#504	The feature map on the site’s landing page (site/src/pages/index.astro, #504): four groups, each an editorial heading over the Features pages it links, in reading order.
scripts/docs/features/permission-modes.ts	#496	The extension that sets the mode and answers auto’s asks (#496).
scripts/docs/features/questions-and-dialogs.ts	#114	Questions and dialogs (#114): the demo session’s questionnaire, then the permission engine’s prompt, each while pi waits.
scripts/docs/features/spec.ts	#482	A Features page as data (#482): the words, next to the capture steps that prove them.
scripts/docs/flow-diagrams.ts	#188	Generates docs/reference/flows.md (#188): the control plane and the observation pipeline as Mermaid, drawn from the SAME discovery the reference tables use.
scripts/docs/flow-pages.ts	#482	Builds a docs/flows/<id>.md page for every @flow in source (#482).
scripts/docs/flow-tags.ts	#482, #488	What a flow page is built from (#482): tags in source comments and the diagrams tests record.
scripts/docs/gate-source.ts	#170, #262	Reading a declared constant back out of a gate’s source (#170, split out on #262).
scripts/docs/generator-support.ts	#174	What every generator under scripts/docs/ shares (#174): the exhaustiveness check that makes a metadata table refuse to be stale, and the one way a generator runs — its page to stdout, or one name: reason line to stderr and a non-zero exit, never a partial page.
scripts/docs/ported-provenance.ts	#168	Generates docs/seams/ported-provenance.md (#168): one row per file under components/ai-elements/ — the upstream path and commit its header names, and the Modified — line that follows.
scripts/docs/refresh-fences.ts	#162, #168	Refreshes every sourced fence in a page from the source it names (#168): the authoring and repair tool for test/docs-gate.test.ts.
scripts/docs/seams-table.ts	#162, #167, #213	Generates the seams table (#162 workstream 11, #167 item 4) — the block docs/architecture.md embeds between <!-- generated-block: … --> markers.
scripts/docs/site-base.ts	#188, #506	The path the documentation site is served under — ONE value, read by three readers (#188).
scripts/docs/site-content.ts	#188, #213	Projects docs/ into the Starlight site’s content collection (#188).
scripts/docs/site-links.ts	#188	Every internal link in the BUILT site resolves to something the site serves (#188).
scripts/docs/source-citations.ts	#482	SOURCE CITATIONS IN THE HAND-WRITTEN DOCS (#482): path#Name in a code span, never a line number.
scripts/docs/source-comments.ts	#482, #488	Every comment in a source file, with what it is about, taken from the TypeScript syntax tree (#482, PR #488 review): the docs builders read comments the way the compiler does, never by matching text.
scripts/docs/source-constants.ts	#482	A top-level constant’s VALUE, read out of a source file with the TypeScript parser (#482).
scripts/docs/touched-comments.ts	#482	The comments a pull request has to answer for (#482): every comment whose own lines it changed, and every comment on a declaration it changed, found from git diff and the TypeScript syntax tree (source-comments.ts).
scripts/docs/verification-inventory.ts	#170, #262	Generates docs/reference/verification-inventory.md (#170): enforcement gates, the numeric and count ratchets they carry, and the deliberately reusable test doubles.
scripts/enso-eval.ts	#441	A thread’s session eval (#441), from the running server’s GET /api/threads/:id/eval.
scripts/enso-launch.ts	#221	The terminal launcher’s decisions, apart from the launch (enso.ts spawns; this decides): the isolation triple as pi’s arguments, the print-run trigger, and whether the pi it is about to spawn is one the guard was pinned against.
scripts/enso-logs.ts	#132	See the log (#132): the day’s file, rendered the way the terminal renders it live.
scripts/enso-thread.ts	#86, #97	Inspect the live web server’s threads from a shell — the agent’s half of #86.
scripts/enso.ts	#20, #217, #446, #496	Launch a VANILLA pi with only Enso loaded.
scripts/gate.ts	#188, #208, #257, #342, #482	Ported from slop-factory’s bun example (examples/bun/scripts/gate.ts) — the shape is deliberately identical so improvements travel in either direction.
scripts/link-vendor-packages.ts	#30	Ensure the vendor pi packages exist inside the harness package’s own node_modules.
scripts/lint/process-environment.ts	#89	The environment boundary (#89): every file allowed to read the real process environment.
scripts/print-harness.ts	#9, #13, #20, #496	The PRINT-MODE harness variant (#20, #496): the Enso package minus the permission engine (@gotgenes/pi-permission-system).
scripts/source-tree.ts	#162, #174	The one walk over the source tree (#174, #162 workstream 6: one walker per gate family).
test/api-group-gate.test.ts	#188	THE API PAGE IS ORGANISED BY SEAM, AND THAT ORGANISATION IS HELD (#188).
test/browser-bundle-gate.test.ts	#211	The browser zone must bundle for the browser (#211).
test/check-coverage.test.ts	#53	The coverage GATE’s own arithmetic (#53 S2).
test/code-offenders.test.ts	#162	The allowlist is the leak inventory (#162 workstream 4): a row hides a file’s matches, and a row for a file with no matches is drift and is reported.
test/complexity-ratchet.test.ts	#264	Re-measures the cognitive-complexity pins, per FUNCTION (#264).
test/dependency-gate.test.ts	#218, #223	What the dependency manifests claim, held against what the code actually imports (#218, #223).
test/docs-gate.test.ts	#162, #167, #168, #258	The docs cannot drift (#168, goals §3.3): a page either quotes source and is checked against it, or is generated from source and is diffed against it.
test/duplicate-shapes-gate.test.ts	#53, #174, #255	One place for every shape: no TypeBox schema is declared outside @enso/core (#53, #255).
test/e2e-selectors.test.ts	#116, #277	THE E2E SELECTOR CONTRACT (#277).
test/fallow-config.test.ts	#163	fallow’s entry list cannot drift from the harness manifest (#163).
test/feature-pages.test.ts	#482	A FEATURES PAGE IS BUILT ONLY FROM FACTS ITS SPEC STILL MATCHES (#482).
test/features-gate.test.ts	#277, #437, #482	THE FEATURES PAGES DESCRIBE A UI THAT EXISTS (#437).
test/flow-pages.test.ts	#482	FLOW PAGES ARE BUILT FROM TAGS, AND THE TAGS MUST AGREE (#482).
test/gate-abort.test.ts	#157	The gate’s blind spot, closed (#157): a tool that dies mid-run and still exits 0.
test/gate-support.ts	#150, #162, #165, #174	What the source-tree gates share (#165, #162 workstream 6): the word-splitter, the sequence matcher, the comment skip, over the one walker (scripts/source-tree.ts, #174).
test/glossary-doc.test.ts	#161, #164, #165, #245	The glossary keeps its own three rules (#161, PR #164 review; #245).
test/glossary-gate.test.ts	#165, #241, #257, #287	The glossary’s Retired table, applied to the source tree (#165, docs/glossary.md → Retired).
test/harness-barrel-gate.test.ts	#173, #251, #263	THE HARNESS BARREL IS ITS CONSUMPTION, AND THAT IS CHECKED (#263).
test/logging-gate.test.ts	#132, #162, #254	Every record goes through the one logger (#132), and the substrate stays behind it.
test/mermaid-gate.test.ts	#188	EVERY DIAGRAM IN THE DOCS PARSES (#188).
test/naming-gate.test.ts	#82, #83, #250	The naming gate’s exemption for externally-fixed KEYS (#82, PR #83 review), and the severity that decides whether a tier blocks (#250) or merely mentions.
test/no-lint-suppressions.test.ts	#82	The gate may not be talked out of, one line at a time.
test/presentation-gate.test.ts	#31, #121, #174, #253	Presentation stays presentation (#121 item 4, #31).
test/scripts-extensions.test.ts	#269, #308	scripts/ is TypeScript, with nothing left to except (#269, #308).
test/secret-scan-gate.test.ts	#209	The range .github/workflows/secret-scan.yml hands gitleaks is the coverage of the only gate that stops a committed secret, so it is asserted here rather than read (#209).
test/site-gate.test.ts	#188, #213	THE SITE IS A PROJECTION OF docs/, AND THE PROJECTION IS TOTAL (#188).
test/source-citation-gate.test.ts	#482	A HAND-WRITTEN PAGE POINTS AT CODE BY DECLARATION, AND EVERY POINTER HOLDS (#482).
test/source-comments.test.ts	#482, #488	WHICH DECLARATION A COMMENT IS ABOUT, FROM THE SYNTAX TREE (#482, PR #488 review).
test/source-constants.test.ts	#482	A docs page quotes a constant another zone owns by reading its source (#482).
test/touched-comments.test.ts	#482	WHICH COMMENTS A DIFF PUTS AT RISK (#482).
test/vendor-gate.test.ts	#69, #145, #150, #165, #173, #215	The seam has an owner: only the host and the pi extensions may name the vendor (#145).

Parser limit. The parser considers the first block or contiguous line comment beginning within the first 80 lines of TypeScript/JavaScript source under packages/, scripts/, and test/. It skips generated type output, dependencies, coverage output, and vendored web components. Sentence reduction uses the first ., !, or ?, optionally followed by closing quotes/brackets and then whitespace or the end of the header; a qualifying header that does not fit that current source shape is emitted as UNCLASSIFIED and makes generation fail.