[github-actions]

Closes #1600. Submitted by @SkylabsTechnology.

Ready for artifact review. The reviewer will resolve the submitted source and complete the registry listing.

Submission: submissions/1600.json.
Git references are optional. Use a supplied reference; otherwise resolve main during review. Git updates are submitted manually.

[paseo-bot]

Turn Review 1.3.0 is approved, @SkylabsTechnology. I pinned the commit you confirmed on the submission issue, preserved plugin/, switched the listing to your three shipped images, and removed the intake file. Nothing else is required for this release.

For the next release, update your overview’s minimum Paseo version to 0.13.2 and describe the optional multi-agent rollback setting and its concurrent-edit warning, so the listing matches the manifest and settings. Listing-page guidance.

Review data

• Policy: main REVIEW.md blob 3c5e763c9565b93ea33fa48c9aeb83e415c72d67. Read the PR, submission #1600, its author’s commit confirmation, and accepted original #1248 / #1247. Original and current submitter GitHub account IDs match: 88116355.
• Initial registry head 87434f4cd7d9c7ef4d2b462442a5d58911ad1947; completed reviewed head 84c30a5cd9f539d62bc5513fd78da7e997c25785. Git artifact https://github.com/SkylabsTechnology/turn-review.git, directory plugin, exact commit ed338073cf793d2cb586a7526fd7cfb0e155f930, version 1.3.0. Initially resolved repository HEAD (master, no main exists); the author subsequently confirmed exactly this revision on the issue. No tag required or selected.
• Independently fetched and compared accepted 04aa8265417d20d9d455cfb4e55408f2e4d31ee7 and the proposed artifact without hooks/submodules. Git archive SHA-256 old 71d2013cff75d1e1f4bab146a9b9de22b3dd346307ad68bd9cb0e5c9814c65f7, new a5a800fe2a55fd99ad6b1131eb045fd5fdd2b6f16118eb6c81ca1492360bcd1e. Checked all 55/65 archive members before extraction.
• Inspected changed production files and affected snapshot, path classification, rollback transaction, recovery, journal/GC, lock, RPC/settings and UI flows. Read both entries, Git adapter and storage for context. Local imports and required entries exist. The new palettes are static color data; captured code remains React text, not executed HTML or code.
• Turn events capture eligible Git worktree files into local owner-only snapshot storage. Sensitive-name and configured deny rules exclude matching paths; this does not establish that every possible secret is recognized. The changed reader uses no-follow when available, regular-file checks and resolved-path containment. These checks are not an atomic filesystem boundary against every concurrent path replacement.
• User-triggered Deny/Undo/Restore writes or deletes the selected reviewed file. Complete captures, enabled write mode, repository identity, agent status and live hashes gate rollback; the transaction backs up bytes, journals preparation, rechecks under a repository lock, stages replacements with random exclusive/no-follow names, and verifies readback. New mode recording preserves permission bits on replacement/recreation. Recovery now also handles a previously deleted file, including reapplying deletion, while the restore window remains open; GC retains its recovery data.
• Multi-agent rollback is off by default. Enabling it explicitly skips the overlap-attribution refusal, retaining the other gates; its settings text warns that Deny can revert another agent’s concurrent edits to the same file. Same-agent orphaned starts become interrupted/unsupported. The new fixture writer authorization defaults off, requiring explicit test/environment opt-in as well as ordinary write/path gates. Detected journal parse corruption refuses writes/compaction; lock owner liveness and heartbeat reduce stale-lock reaping during legitimate writes. No blanket crash/race safety guarantee is claimed.
• No new network or credential-access path, runtime downloader, shell construction or eval found in the inspected changes. Existing Git subprocesses use fixed argument arrays for repository identity/status/capture, serving the review purpose. Filesystem rollback and local snapshot retention are intentional disclosed behavior, disabled for writes by default.
• No manifest build/preparation command or production dependencies. Runtime imports use Node built-ins and host libraries. Plugin development lock has 347 exact npm registry entries with integrity; esbuild/fsevents lifecycle markers are development-only. No plugin/dependency code installed, built, imported or executed.
• Registry edits: updated both commit pins and review date, retained original attribution/categories/submission/publication dates, removed obsolete registry media overrides so the new manifest supplies all three packaged PNGs, and removed submissions/1600.json. Viewed all three sample interface images. Author description/overview retained; no redundant registry copy.
• Trusted main scripts/workflows match the branch. Committed-tree online validation passes: 435 well-formed records, one matching changed artifact, none skipped. The same trusted registry scripts passed all 189 local tests earlier in this execution; final-head CI also passed. Approved the intake’s held validation run. No factory incompatibility found.
• Limits: static inspection only; no runtime/UI/rollback QA, dependency installation or execution. Read shipped security/crash/recovery and multi-agent regressions without running them. No exhaustive audit of external tools, OS behavior or every existing code path; concurrent external writes and hostile filesystem races are not proven safe by this review.