@hraness/slopcamera 3.2.4

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Hraness contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/NOTICE.md

@@ -0,0 +1,60 @@
+# Notices
+
+Slopcamera is an independent project and is not affiliated with or endorsed by
+tldraw, Inc.
+
+The runtime package does not include the tldraw SDK or tldraw Offline. It writes
+the documented `.tldr` JSON interchange format so that users can import a
+diagram into compatible tldraw software. The development test suite optionally
+uses the upstream `tldraw` package to check compatibility; that package remains
+under the [tldraw license](https://tldraw.dev/community/license).
+
+The optional `slopcamera canvas install` command downloads an unmodified installer
+from the official
+[`tldraw/tldraw-offline`](https://github.com/tldraw/tldraw-offline) GitHub
+release and verifies the SHA-256 digest published by GitHub. tldraw Offline is
+not open source and remains subject to its own terms.
+
+tldraw and its associated marks are trademarks of tldraw, Inc.
+
+Raster output uses
+[`@resvg/resvg-js`](https://github.com/yisibl/resvg-js), distributed under the
+Mozilla Public License 2.0. It is installed as a separate runtime dependency
+and is not relicensed by this project.
+
+Default diagram and caption typography uses the unmodified Nebula Sans Book
+and Bold fonts, distributed under the SIL Open Font License 1.1. The npm
+package retains the upstream license and provenance in
+`src/assets/fonts/nebula-sans/`.
+
+Raster-to-SVG conversion uses
+[`VTracer`](https://github.com/visioncortex/vtracer), distributed under the MIT
+License. The package does not bundle VTracer. On first use it downloads an
+unmodified macOS or Linux platform archive from the official VTracer 0.6.4
+GitHub release, verifies both archive and extracted binary SHA-256, and caches
+the binary outside the package.
+
+Raster decoding and fidelity measurement use
+[`sharp`](https://github.com/lovell/sharp), distributed under the Apache
+License 2.0. Sharp's prebuilt
+[`libvips`](https://github.com/libvips/libvips) dependency is distributed under
+the GNU Lesser General Public License 3.0 or later. Both remain separately
+installed runtime dependencies and are not relicensed by this project.
+
+Optional model-backed generation uses
+[`@ai-sdk/gateway`](https://www.npmjs.com/package/@ai-sdk/gateway) and the
+[`ai`](https://www.npmjs.com/package/ai) SDK. Prompts and referenced media are
+sent to Vercel AI Gateway and the model provider selected by the caller, under
+those services' terms. Slopcamera does not operate an intermediary generation
+service.
+
+The production `slopcamera.com` browser bundle includes
+[`posthog-js`](https://github.com/PostHog/posthog-js), distributed under its
+combined Apache License 2.0 and MIT terms. The fingerprinted bundle carries the
+upstream license text generated from the exact locked package.
+
+The complete local workflow host uses
+[`Effect`](https://github.com/Effect-TS/effect), distributed under the MIT
+License (Copyright 2023 Effectful Technologies Inc). It remains a separately
+installed runtime dependency and is not relicensed by this project. Portable
+workflow authoring and graph compilation do not load this runtime.

package/PRIVACY.md

@@ -0,0 +1,46 @@
+# Privacy and local data
+
+`@hraness/slopcamera` is a local-first media authoring toolkit for work that the
+operator owns or is authorized to record, import, edit, analyze, and publish.
+This document describes the data it can capture, the local execution boundary,
+and the selected media that can leave the machine.
+
+On macOS, Slopcamera can request permission to record selected displays, system
+audio, a selected camera, and a selected microphone. When interaction metadata
+is enabled, it can record cursor positions, clicks, key activity, focused-input
+bounds, display topology, and changed window snapshots. Typed-text collection
+is separately opt-in. Slopcamera suppresses secure fields even when typed-text
+collection is enabled.
+
+Slopcamera can also read caller-selected local media and project files, invoke
+bounded local browser and media subprocesses, analyze faces locally without
+identifying them, and write recordings, derived media, metadata, previews, and
+receipts below a caller-selected project. Its local MCP server and workflow
+host expose fixed, typed operations to an authorized local agent. Explicitly
+imported imperative workflow modules are trusted current-user Bun code rather
+than sandboxed input.
+
+Generation and model-backed media analysis can send an explicit prompt and
+caller-selected media to Vercel AI Gateway. Local media upload requires the
+matching command acknowledgement. Local vectorization, face detection,
+ordinary media editing, diagram rendering, and capture remain local. Slopcamera does
+not provide an account service and does not upload a project to a Slopcamera
+service.
+
+Use Slopcamera only on devices, accounts, displays, conversations, and media that you
+are entitled and permitted to capture or process. Obtain any consent required
+by law, contract, workplace policy, or platform rules. Do not use Slopcamera to
+surveil another person, collect credentials, bypass operating-system
+permissions or access controls, capture protected communications without
+authorization, or publish private media without permission.
+
+Screen recordings, camera and microphone media, system audio, cursor and input
+events, typed text, window titles, focus state, project paths, model prompts,
+and generated receipts can contain credentials, private communications,
+personal data, or proprietary material. Review captured and derived artifacts
+before committing, sharing, uploading, or publishing them. Keep Gateway
+credentials in the process environment and remove secrets and private media
+from vulnerability reports.
+
+Report suspected vulnerabilities through GitHub private vulnerability
+reporting at https://github.com/hraness/slopcamera/security/advisories/new.

package/README.md

@@ -0,0 +1,311 @@
+# Slopcamera
+
+[![Slopcamera: a visual studio for coding agents](https://slopcamera.com/og.png)](https://slopcamera.com)
+
+**Slopcamera is a local visual studio for coding agents. Author scenes, combine
+generated and recorded media, and export images, diagrams, animation, and video
+from retained sources.**
+
+Describe a finished result to Codex, Claude, or another coding agent. Slopcamera gives
+it a Bun CLI, TypeScript SDK, and version-matched Agent Skill to inspect sources,
+direct cameras, edit a composition, and render the result. A separate MCP server
+exposes a fixed diagram and image toolset. There is no Slopcamera account or hosted
+project database.
+
+[Install](#install-slopcamera) · [Make a first diagram](#make-your-first-diagram) · [Capabilities](#what-slopcamera-does) · [Documentation](docs/README.md) · [slopcamera.com](https://slopcamera.com)
+
+## Why Slopcamera
+
+- **Keep creative work editable.** Native scenes, portable scenes, diagrams,
+  and video projects retain their own sources and settings. Rendered frames
+  and portable assets are derivatives; a video of a character does not retain
+  its rig.
+- **Give agents explicit operations.** Inspect a project, name a camera, plan
+  a render, review a candidate, and select a result. The CLI returns structured
+  results and keeps operation receipts that identify inputs and outputs.
+- **Revise without replacing the originals.** Normal media edits record cuts,
+  timing, framing, captions, and effects as project decisions. Preview and final
+  renders use the same timeline and composition.
+- **Choose where computation happens.** Local rendering and editing use your
+  machine. Optional model-backed work uses your Vercel AI Gateway access, with
+  explicit acknowledgement before named local media is uploaded. Native Python
+  authoring requires separate trust because it runs as your current user.
+
+## Install Slopcamera
+
+Slopcamera currently installs from source. No renamed release archive has been
+published. Install [Bun 1.3.14 or newer](https://bun.sh) and Git, then use a new
+checkout:
+
+```sh
+git clone --branch main https://github.com/hraness/slopcamera.git slopcamera-source
+cd slopcamera-source
+git rev-parse HEAD > ../slopcamera-source-commit.txt
+bun install --frozen-lockfile --ignore-scripts
+bun run build:sdk
+bun run build:desktop:cli
+```
+
+Keep the checkout and recorded commit. In this shell, define the command against
+that exact build:
+
+```sh
+export SLOPCAMERA_SOURCE_ROOT="$PWD"
+slopcamera() { bun "$SLOPCAMERA_SOURCE_ROOT/apps/desktop/dist/cli/main.js" "$@"; }
+slopcamera --help
+slopcamera doctor --json
+slopcamera skill install --target agents
+```
+
+Use `--target claude` for Claude Code or omit the target for Codex. Add
+`--scope project` inside the target repository for a project-only skill install.
+The skill comes from the same checkout as the CLI. Start a new agent session
+after installation. In a later shell, restore the checkout path and function.
+
+Native engines install separately. The [source-install guide](docs/how-to/use-current-source.md)
+explains workspace placement and durable-run identity; the
+[capability reference](docs/reference/capabilities.md) names runtime requirements.
+
+<details>
+<summary>Historical Atet release evidence</summary>
+
+[Atet v3.2.3](https://github.com/hraness/atet/releases/tag/v3.2.3) and its
+[original archive](https://github.com/hraness/atet/releases/download/v3.2.3/hraness-atet-3.2.3.tgz)
+remain historical publication evidence. Those immutable bytes install Atet,
+not Slopcamera. Renaming the repository does not create a renamed package or
+change an existing release.
+
+</details>
+
+## Make your first diagram
+
+After the source build above, this local task needs no model account. In a new directory,
+create the included diagram, check it, and render it:
+
+```sh
+mkdir slopcamera-first
+cd slopcamera-first
+slopcamera diagram init first.diagram.json
+slopcamera diagram check first.diagram.json --strict
+slopcamera diagram render first.diagram.json
+```
+
+You now have `example-flow.tldr`, `example-flow.light.svg`,
+`example-flow.dark.svg`, `example-flow.light.png`, and
+`example-flow.dark.png`. Open a PNG to inspect the result. The JSON remains
+editable, and the `.tldr` file is editable tldraw interchange. Rendering again
+replaces those five derived files.
+
+Follow [Your first diagram](docs/tutorials/first-diagram.md) to change a label and
+see the result. For a moving 3D subject, use [Directed scenes](docs/spatial-scenes.md).
+For detailed native 3D from the current source build, follow
+[Your first native film](docs/tutorials/first-native-film.md).
+
+## What Slopcamera does
+
+### Author scenes and direct cameras
+
+Place geometry, images, video, diagrams, and text in a portable scene. Inspect
+stable part IDs, make typed edits, select a named camera, and render frames,
+contact sheets, or video. The Three.js profile includes calibrated cameras,
+explicit animation, supported GLB geometry, and an explicitly selected hardware
+GPU path. Spark admits saved splat worlds for local camera direction.
+
+> Create a short product reveal. Keep the model editable, orbit the camera,
+> mount the product diagram on a screen in the scene, and show me contact frames
+> before rendering the video.
+
+The portable GLB profile has a defined geometry and material subset. Saved splats
+capture appearance; they do not establish collision geometry or editable native
+meshes. See [Directed scenes](docs/spatial-scenes.md).
+
+### Film native worlds and educational animation
+
+The current source build can direct Blender for detailed sets, materials,
+lighting, skinned characters, cloth and liquid caches; CadQuery for parametric
+solids and STEP; and Manim Community for mathematical animation. Seven editable
+starters include a product, character, shaded street, cloth, liquid, CAD bracket,
+and educational presenter.
+
+> Build a shaded street with an original presenter. Explain the idea with an
+> animated diagram mounted in the world, then pull the camera back into the
+> city. Keep the native scenes and diagram sources for later edits.
+
+Native source and exact job settings remain retained. Verified frames can become
+an ordinary project clip. `slopcamera scene camera-track` samples an explicit
+camera clock for reuse. Supported GLB derivatives and calibrated cameras can
+cross between native and portable scenes; rigs, solvers, and procedural materials
+remain native. Blender and Python environments are installed separately, and
+source execution requires explicit current-user trust. See [Native film studio](docs/studio.md)
+and [Make an educational video](docs/how-to/educational-video.md).
+
+### Build diagrams and motion graphics
+
+Create editable diagrams with tldraw, SVG, and PNG outputs, or turn raster artwork
+into SVG locally with VTracer. Animate graphic layers with HTML, SVG, Motion,
+p5, Two, Paper Shaders, or Three.js. Outputs can stand alone or join a video
+project. The optional vgpu example renders programmable WebGPU passes into
+retained raster frames for use on a world-space screen.
+
+Use `slopcamera html catalog` to inspect the admitted local creative tools. The
+[creative toolkit reference](docs/html-overlay-creative-toolkit.md) distinguishes
+available profiles from upstream possibilities. vgpu does not enable shared GPU
+textures or a Three WebGPU renderer inside the current WebGL2/Spark profile.
+
+### Generate and direct media
+
+Discover image, video, speech, and transcription models through your own Vercel
+AI Gateway access. Generate images from text and references, add a voiceover,
+transcribe sound, or create video shots using the selected model's supported
+inputs. Availability and pricing come from the live catalog.
+
+The current source build also provides `direct` shot recipes: retain a film
+budget across attempts, review each take before accepting it, and use an accepted
+clip's last decoded frame as the next shot's reference. Changed predecessors
+invalidate affected continuations while earlier paid results remain retained.
+Model continuity is reviewed, not guaranteed. Budget estimates are not a provider
+billing cap.
+
+See [Generate media](docs/how-to/generate-media.md), [Direct short generated clips](docs/directing-video.md),
+and [Gateway configuration](docs/vercel.md). Generation uses caller-owned access;
+uploading local references requires the matching explicit acknowledgement.
+
+### Edit footage and deliver finished videos
+
+Record a screen, camera, microphone, and system audio on macOS, or import existing
+footage. Remove pauses and filler words, align sound, reframe speakers, zoom into
+screen actions, and add captions, graphics, color, and audio treatment. Preview
+candidates before selecting a result, then export clean and captioned versions
+in 16:9, 9:16, 1:1, and 4:5 from the same edit.
+
+> Edit my product demo: cut the pauses, zoom into each important click, keep the
+> speaker framed, add captions and `logo.svg`, and show a preview before export.
+
+Recording requires the corresponding macOS permissions. Input-event capture can
+include clicks, cursor movement, key activity, and focused-input information;
+typed-text capture is separately opt-in and secure fields are suppressed. Read
+[`PRIVACY.md`](PRIVACY.md) before recording sensitive material.
+
+Start with [Edit a video](docs/how-to/edit-video.md) or inspect a reusable recipe:
+
+```sh
+slopcamera workflows list --json
+slopcamera workflows show social-variants --json
+```
+
+## How Slopcamera works
+
+Keep the source that owns each creative decision. A native scene owns a rig or
+simulation; a portable scene owns supported geometry, cameras, and media surfaces;
+a diagram owns its objects and labels; a video project owns cuts and delivery.
+SLOPCAMERA connects these through explicit assets and rendered derivatives.
+
+1. **Prepare the sources.** Import footage and assets or author a scene, diagram,
+   or native program. Inspect available tools before choosing an engine.
+2. **Direct the result.** Name cameras, shots, timing, composition, and output
+   settings. Generate missing media only when the job calls for it.
+3. **Review a render.** Inspect contact frames, motion, captions, sound, and
+   continuity. Preserve candidates and select the approved result.
+4. **Deliver and revise.** Export the required formats and retain source paths,
+   project decisions, and operation receipts for the next change.
+
+### Instructions for coding agents
+
+Read local project instructions and inspect sources before changing them. Use
+`slopcamera --help`, `slopcamera doctor --json`, `slopcamera operations list --json`, and the
+installed skill to discover the exact local surface. Agree on material output
+requirements, preview substantial changes, inspect the resulting files, and
+report their paths. Do not infer provider access, native trust, or model quality
+from a successful plan.
+
+[Run agent workflows](docs/how-to/run-workflows.md) covers reusable recipes,
+declarative graphs, approvals, and resuming work.
+
+## Important limitations
+
+- **Runtime support varies.** The CLI uses Bun on macOS, Linux, and Windows;
+  capture is macOS-specific. Media, browser, GPU, and native studio profiles
+  have additional requirements. Use the capability reference and `slopcamera doctor`.
+- **Interchange preserves a supported subset.** Native rigs and simulations do
+  not become editable Three scenes by exporting a GLB. An image or video on a
+  plane supplies pixels, not hidden geometry. Calibrated camera exchange does
+  not match lighting, depth of field, or color treatment automatically.
+- **Generated media requires review.** Models may change subject identity,
+  motion, or text. Saved AI worlds are appearance assets, not validated robotics
+  or reinforcement-learning environments.
+- **Trusted code is not sandboxed.** Native Python and caller-authored Bun
+  workflows run with the current user's access. Hashes and receipts identify
+  observed inputs and outputs; they do not make arbitrary code hermetic.
+- **MCP is a subset.** Its fixed tools check and render diagrams, vectorize
+  images, and generate images. It does not expose every local CLI operation.
+
+## Design and trust
+
+There is no Slopcamera account, hosted project database, or browser generation service.
+Ordinary editing and rendering remain local. Gateway generation and selected
+cloud analysis use credentials from the local process and request explicit
+acknowledgement before uploading named media. This website never accepts a
+Gateway credential. Native Python requires separate authorization. Custom Bun
+workflow modules execute when loaded, including during check and plan; review
+their source first. Both have the current user's access, including potential
+network access, outside the normal media-operation boundary.
+
+Original media remains unchanged by normal edit operations. Projects retain
+explicit revisions, and important operations record their inputs and outputs.
+Native tools, providers, codecs, and GPU drivers can affect results, so retained
+source identity alone does not promise identical pixels on another machine.
+
+See [Architecture](docs/architecture.md), [`SECURITY.md`](SECURITY.md),
+[`PRIVACY.md`](PRIVACY.md), and [`NOTICE`](NOTICE) for the detailed boundaries.
+
+## Documentation
+
+- **Learn:** [Your first diagram](docs/tutorials/first-diagram.md) · [Your first native film](docs/tutorials/first-native-film.md).
+- **Make a result:** [Edit video](docs/how-to/edit-video.md) · [Generate media](docs/how-to/generate-media.md) · [Run workflows](docs/how-to/run-workflows.md) · [Educational video](docs/how-to/educational-video.md).
+- **Look up support:** [Capabilities and release availability](docs/reference/capabilities.md) · [SDK entrypoints](docs/reference/sdk.md) · [Creative tools](docs/html-overlay-creative-toolkit.md).
+- **Understand the system:** [Architecture](docs/architecture.md) · [Native studio](docs/studio.md) · [Directed scenes](docs/spatial-scenes.md).
+
+The [documentation index](docs/README.md) connects these paths.
+
+## For software integrations
+
+Run this example with Bun from the source checkout after `bun run build:sdk`.
+The checkout resolves its own `@hraness/slopcamera` package exports.
+
+SDK imports do not start the CLI or inspect local project state. For example,
+convert an existing local image into an SVG:
+
+```ts
+import { vectorizeImage } from "@hraness/slopcamera"
+
+const result = await vectorizeImage("logo.png", { outputPath: "logo.svg" })
+console.log(result.receipt.sourceSha256, result.receipt.svgSha256)
+```
+
+Use `@hraness/slopcamera/code` for declarative workflow graphs,
+`@hraness/slopcamera/workflow` for trusted Bun workflows, and `@hraness/slopcamera/local/*`
+for the local media engine. See the [SDK reference](docs/reference/sdk.md) for
+entrypoint scope and execution effects.
+
+## Verification
+
+```sh
+bun install --frozen-lockfile --ignore-scripts
+bun run check
+```
+
+The required check covers public SDK boundaries, the local runtime, schemas,
+Agent Skill, generated entrypoints, static site, deterministic and property
+tests, and packed consumers. Native and provider-dependent profiles require
+their corresponding external qualification; a local unit-test pass does not
+establish them. See [`CONTRIBUTING.md`](CONTRIBUTING.md) for the complete gates.
+
+## Contributing
+
+Read [`CONTRIBUTING.md`](CONTRIBUTING.md) and the nearest `AGENTS.md` before
+changing a package or runtime boundary. Report vulnerabilities through
+[`SECURITY.md`](SECURITY.md).
+
+## License
+
+[MIT](LICENSE), with third-party notices in [`NOTICE`](NOTICE).

package/SECURITY.md

@@ -0,0 +1,21 @@
+# Security
+
+Report suspected vulnerabilities privately through [GitHub’s security advisory form](https://github.com/hraness/slopcamera/security/advisories/new). Do not open a public issue for credential exposure, path escape, unsafe SVG output, archive extraction, subprocess containment, unbounded resource use, Gateway authority substitution, or MCP boundary failures.
+
+Include the affected version, platform, command or API, minimal reproduction, expected boundary, observed result, and whether any secret or caller-owned media left the machine. Remove tokens, account identifiers, private paths, and proprietary media from the report.
+
+Slopcamera’s local MCP server confines paths to one caller-selected root but is not an operating-system sandbox against concurrent same-user mutation. Vectorization is network-silent. Generation sends its prompt and explicitly supplied media directly to Vercel AI Gateway. Slopcamera reads `AI_GATEWAY_API_KEY` or `VERCEL_OIDC_TOKEN` from the process environment and never persists either value.
+
+An explicitly imported workflow module is trusted Bun code with the authority of the current user. Review workflow modules before running them. Declarative graph compilation restricts operation nodes to the closed capability projection supplied by the host and rejects unsupported capabilities before executor or resource admission, but it does not sandbox the JavaScript that constructs the graph.
+
+The macOS host can request Screen Recording, System Audio Recording, Camera,
+Microphone, and Input Monitoring permissions. Its input-event metadata and
+recordings can contain selected display pixels, system audio, camera video,
+microphone audio, cursor movement, clicks, key activity, focused-input bounds,
+display topology, and changed window snapshots. Typed text is captured only
+when separately enabled, and secure fields are suppressed even then. Treat all
+capture output as sensitive, obtain the required consent, and inspect it before
+sharing or uploading it.
+
+The [privacy guide](PRIVACY.md) describes captured data, local processing,
+selected uploads, and how to handle sensitive artifacts.