@playola-radio/slipstream 0.1.0

package/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,132 @@
+# Slipstream
+
+**Review your coding agent's work as it happens, instead of facing a pile of
+files at the end.**
+
+Slipstream streams the changes an AI coding agent makes to your code, live, so
+you can follow along and review in near-real-time while the agent works. The name
+is the thesis: a slipstream is the low-pressure pocket behind a fast-moving
+object, and riding in it makes following far cheaper than leading.
+
+Status: **pre-implementation.** The architecture is settled and the MVP plan is
+written. No code yet.
+
+- [`IMPLEMENTATION_PLAN.md`](IMPLEMENTATION_PLAN.md) — the five-stage MVP plan
+- [`NOTES-architecture.md`](NOTES-architecture.md) — decision record, verified
+  findings, and the Codex adversarial review
+
+## Install
+
+```sh
+npm install -g @playola-radio/slipstream
+```
+
+Node.js 24 or newer is required. The published package ships compiled
+JavaScript; developing in this repo still runs the TypeScript sources directly
+(`npm run slipstream`, `npm test`) with no build step. To put a clone on your
+PATH with `npm link`, run `npm run build` first, and again after pulling: the
+linked command runs the compiled `dist/`, not the sources.
+
+## License
+
+Apache-2.0. Copyright Playola Radio, Incorporated. See [`LICENSE`](LICENSE).
+
+## What it promises — and does not
+
+> Slipstream streams **a live history of observed filesystem states, with
+> explicit coverage gaps.** It does not claim to be a complete record of every
+> write.
+
+Capture is watcher-primary, so it observes states rather than writes. If a file
+goes `A → B → C` faster than it can be read, Slipstream reports `A → C`; an
+`A → B → A` cycle can be invisible entirely. Those gaps are disclosed in the
+event schema and surfaced in the UI rather than papered over.
+
+Similarly, attribution is revisable inference with an explicit status
+(`pending` / `heuristic` / `ambiguous` / `unknown`), never a verified claim of
+authorship. A timestamp near an agent's tool call is evidence, not proof.
+
+## Design constraints
+
+- **The event schema is the public interface.** The on-disk JSONL log plus
+  content-addressed blobs are the source of truth; the HTTP/SSE reader is a thin
+  view over them; the bundled UI is one client among possible many. You must be
+  able to delete the front-end and replace it.
+- **Slipstream does not launch agents.** Conductor stays the launcher.
+  Slipstream rides in through user-level MCP and skill configuration.
+- **Claude Code and Codex CLI from day one**, via a capture path that does not
+  depend on either.
+
+## Architecture
+
+A headless local daemon (TypeScript/Node) captures bytes and writes an
+append-only event log; a browser client (React + Monaco) renders the feed. The
+MCP server is a thin stdio forwarder per agent session — verified necessary,
+since each session spawns its own server process — and the daemon owns the store.
+
+
+## Queue a question about a captured change
+
+With the shared daemon running (`slipstream start`) and explicitly attached to a
+Claude Code or Codex session, an independent local client can queue a question:
+
+```sh
+slipstream ask --store /path/to/store --session <capture-uuid> \
+  --request-id <caller-generated-lowercase-uuid> --input question.json
+```
+
+`question.json` contains the question and immutable after-snapshot identity read
+from the public events API (sequence numbers are decimal strings):
+
+```json
+{
+  "text": "Why is this check needed?",
+  "context": {
+    "change_seq": "42",
+    "path": "src/example.ts",
+    "snapshot_sha256": "aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
+    "line_start": 3,
+    "line_end": 5
+  }
+}
+```
+
+A follow-up adds `"reply_to_question_id"` naming the earlier question; its
+`context` must be identical. The example hash is a placeholder: use the actual change's `after.sha256`. The
+daemon validates the durable event and original blob, derives the selected text,
+and copies the explicit attach target. It never reads the current working file
+or accepts client-supplied authorship. Only after-content up to 1 MiB is eligible;
+select at most 200 lines / 16 KiB. Questions are trimmed and capped at 8192 UTF-8
+bytes. `serve` has no attach/control path and does not support `ask`.
+
+Success prints JSON `{v:1,ok:true,session_id,request_id,question_id,seq,
+queued_at_ms,expires_at_ms,duplicate}`. It means **durably queued**, not delivered
+to an agent or answered. Read `slipstream.question.queued.v1` through the existing
+authenticated `GET /v1/sessions/<id>/events` endpoint; its self-contained schema is
+available at `GET /v1/schemas/slipstream.question.queued.v1`.
+
+Codex and Claude Code delivery require an explicit root transcript binding at
+`attach` and a `PostToolUse` hook configured before the chat starts. See
+[the delivery contract](docs/ask-agent/contract.md#delivery-through-posttooluse)
+for the control fields and setup. The public
+`slipstream.question.dispatch_attempted.v1` event means the daemon committed an
+attempt before answering the hook; it does not confirm receipt or an answer.
+Attach Claude shortly after its first root tool call, and keep the chat's
+current directory at the attached worktree when claiming a question.
+
+Retry with the **same request ID, capture ID and input**. Same-ID/body retries
+return the original result without extending the 30-minute TTL. A changed body
+returns `REQUEST_CONFLICT`; more than 16 unexpired questions returns
+`QUESTION_LIMIT`. Other domain errors are `INVALID_QUESTION`, `INVALID_CONTEXT`,
+`SESSION_NOT_SELECTED`, `CAPTURE_NOT_READY`, and `STORAGE_UNAVAILABLE`. Errors
+print structured JSON on stderr (exit 1); local file/syntax errors exit 2.
+`STORAGE_UNAVAILABLE`, or a lost/malformed response after transmission, exits 3:
+the outcome is unknown and the record may already be committed. Preserve the same
+request ID, capture ID and input when retrying. A new capture never resumes an old queue; inspect
+the old public log by `request_id` rather than retargeting a retry.
+
+The control wire request is `{v:1,verb:"ask",session_id,request_id,text,context}`
+over the owner-only `<store>/control.sock` using existing NDJSON framing. No
+harness identity is required from the client. Full details, limits and lifecycle:
+[queue contract](docs/ask-agent/contract.md). Receiving-answer UI remains
+separate work.

package/SKILL.md

@@ -0,0 +1,63 @@
+---
+name: slipstream-begin-task
+description: Use when you start a distinct new task or piece of work in a session — before you begin making the file changes for it — to group those upcoming changes under a titled task in the Slipstream feed. Applies in any harness (Claude Code, Codex, or another) that has the Slipstream MCP server configured.
+---
+
+# Declaring a task to Slipstream
+
+Slipstream shows a human a live feed of the file changes happening in this
+worktree. On its own it sees *states of files*, grouped only by time. When you
+tell it what you are about to work on, it can group the changes you then make
+under that task — which makes the feed legible instead of an undifferentiated
+stream of edits.
+
+## When to use this
+
+Call the `slipstream_begin_task` tool **once, right before you start a distinct
+piece of work** — a bug fix, a feature, a refactor, answering a specific
+request. Declare the task *before* you make its file changes, not after.
+
+Start a **new** declaration whenever you move on to a genuinely different task.
+Each declaration marks the start of its own group; a second task is never a
+retry of the first.
+
+Do **not** call it for every individual edit, and do not re-call it to "resume"
+a task you already declared — one declaration per task is enough.
+
+## How to use it
+
+Call the tool with a short, human-readable title describing the work:
+
+```
+slipstream_begin_task(title: "Fix the off-by-one in the pagination cursor")
+```
+
+A good title is the kind of one-line summary you would put in a commit subject:
+concrete and specific ("Add retry to the upload client"), not vague ("changes"
+or "work"). Then do the work as usual — the changes you make are grouped under
+the task automatically; you do not call anything again to "end" it.
+
+## Reading the result
+
+On success the tool returns identifiers for the task it recorded
+(`session_id`, `task_id`, `event_id`, `seq`). You do not need to act on these;
+they confirm the declaration was committed.
+
+If the tool returns an **error**, read it — it is telling you the truth about
+what happened, and each case wants a different response:
+
+- **`DAEMON_UNAVAILABLE`** — Slipstream is not running for this worktree. This is
+  not a failure of your work; just proceed. Declaring a task is best-effort
+  grouping, never a prerequisite for doing the work.
+- **`SESSION_NOT_SELECTED`** — Slipstream is running but is not currently
+  watching this worktree, so it cannot attribute the task here. Proceed with the
+  work; a human controls which worktree is being watched.
+- **`INVALID_TITLE`** — the title was empty or unusable. Retry once with a real,
+  descriptive title.
+- **`OUTCOME_UNKNOWN`** — the declaration reached Slipstream but its outcome
+  could not be confirmed. **Do not call the tool again for this same task.** A
+  fresh call would create a *second* task, not retry the first. Just continue
+  the work.
+
+In every case: a task declaration is an aid to the human watching the feed. It
+never blocks, gates, or changes the actual work you do.

package/THIRD-PARTY-NOTICES.md

@@ -0,0 +1,36 @@
+# Third-party notices
+
+Third-party components bundled or loaded at runtime, with their licenses kept
+distinct. Slipstream is not itself relicensed by anything here.
+
+## Swift grammar feasibility (T5a.3)
+
+Three separate components, three separate licenses. They are **not** the same
+project and are not conflated:
+
+### tree-sitter-swift (the grammar)
+
+- Project: [`alex-pinkus/tree-sitter-swift`](https://github.com/alex-pinkus/tree-sitter-swift)
+- The grammar compiled into `tree-sitter-swift.wasm`.
+- Declared version range: `^0.4.0`. The exact revision baked into the WASM is
+  not recoverable from the artifact; the sha256 is the real pin (see
+  `SWIFT-GRAMMAR.md`).
+- **License: MIT.**
+
+### tree-sitter-wasms (the wrapper that ships the .wasm)
+
+- Package: [`tree-sitter-wasms`](https://www.npmjs.com/package/tree-sitter-wasms) `@0.1.13`
+- Ships the prebuilt `out/tree-sitter-swift.wasm` this project loads.
+- **License: Unlicense** (public domain dedication). Full text:
+  <https://unlicense.org>.
+
+### web-tree-sitter (the runtime)
+
+- Package: [`web-tree-sitter`](https://www.npmjs.com/package/web-tree-sitter) `@0.25.10`
+- The Tree-sitter WASM runtime that loads and runs the grammar. Already a
+  dependency of the clip parser; T5a.3 reuses it, adding no new runtime pin.
+- **License: MIT.**
+
+The MIT-licensed grammar and runtime and the Unlicense-dedicated wrapper are
+listed apart on purpose: the wrapper's public-domain dedication does not extend
+to the grammar it packages, and vice versa.