tinker-orca@1.3.1

Publisher claims: "Stop editing files one at a time. ORCA drafts every change in parallel, then applies them per-file-serialized so disjoint files fly and shared files never collide. It SPAWNS SUBAGENTS on your own provider (one per unit, which costs money) and writes ONLY the repo-relative files you list. Patches that name any other file are rejected in code. Because a symlinked path component can carry a write outside the repository, a separate checker agent resolves every path before any writer is spawned and again after apply, and lists the change set git can see; code refuses or fails the units it flags. The writers and checkers are ordinary subagents running as your user: the checkers are told not to write and their output is self-reported, and git cannot see writes outside the repository — this is detection, not a sandbox. Committing rewrites git history and needs commit AND confirmedCommit; it is OFF by default and never inferred. In its default mode it creates a git worktree and branch per unit-group and removes them afterwards. It runs an external program ONLY when you pass its absolute path IN THE CALL — no environment variable can name one. See Permissions, Data Flow and Consent." Observed in sandbox: no network, touches nothing outside the project, writes no memory.