cuttingfloor AGENTS.md changelog

https://raw.githubusercontent.com/mvp2o-ai/cuttingfloor/HEAD/AGENTS.md

− - Promote: `scripts/promote-develop.sh "<summary>"` opens the develop → main pull request, waits for its checks and merges it. It versions pending changesets on `develop` first; on `main` the release workflow tags the version and publishes the image. `main` takes nothing but that pull request. Only `develop` may open a pull request into `main` (the Flow check).+ - Tools are agnostic: never name or shape a tool after the thing it acts on or the job it serves. "Remove the logo", "blur the dog" and "brighten the mug" are one chain, as in Photoshop: select (a lasso or shape mask, or an item by its bounds), then act on the selection (show, hide, grade, blur, fill). Bounds and other inputs come from tools that already exist (`track`, `faces`, `judge.ask` boxes). A gap is the one missing verb or fact in such a chain, named for what it does and what it takes (a+ - Promote: `scripts/promote-develop.sh "<summary>"` opens the develop → main pull request, waits for its required checks (not the image build, which gates the server deploy on `main` and skips site-only changes) and merges it. It versions pending changesets on `develop` first; on `main` the release workflow tags the version and publishes the image. `main` takes nothing but that pull request. Only `develop` may open a pull request into `main` (the Flow check).

https://raw.githubusercontent.com/mvp2o-ai/cuttingfloor/HEAD/AGENTS.md

− - Core tenet: tools give the agent actions (edits) and facts it cannot get itself (a transcript, speech spans, frames, loudness); judgment and composition are the agent's. A composition that isn't obvious goes in a skill (`skills/`), a soft harness of steps using the tools. It becomes a script or a tool only on evidence: it is common, agents measurably struggle with the skill, and the tool brings something the agent cannot reproduce. A tool never merges sources or decides behind the agent's back− - Every tool declares its output schema, and results always match it (including the job a long-running tool returns). Agents chain calls in `code.run` before any result exists, so the output signature is the contract; the generated SDK carries it.− - No provider key ever appears in a tool argument, result, error, log or stored file.+ - Core tenet: tools give the agent actions (edits) and facts it cannot get itself (a transcript, speech spans, frames, loudness); judgment and composition are the agent's. A composition that isn't obvious goes in a skill (`skills/`), a soft harness of steps using the tools. It becomes a script or a tool only on evidence: it is common, agents measurably struggle with the skill, and the tool brings something the agent cannot reproduce. A tool never merges sources or decides behind the agent's back+ - Every tool declares its output schema, and results always match it (including the job a long-running tool returns). Clients chain calls (in their own code execution) before any result exists, so the output signature is the contract. cuttingfloor runs no client code: running MCP servers from code is the client's job.+ - No provider key ever appears in a tool argument, result, error, log or stored file. A key the user saves on their account page (their sync. labs key) is kept only as ciphertext (AES-256-GCM, bound to the user, with a server-only secret) in their WorkOS metadata, never on the server's disk, and only its last four characters are shown.