3 Commits

Include renames

Author	SHA1	Message	Date
shadowdaoandClaude Opus 5.5	71ba5076db	docs(acl): reconcile spec prose with the shipped implementation ... Final-wave cleanups from the whole-branch review (final-review.md Minor 1-5): spec §4 now says selective pruning, not "deletes the directory every build"; spec §3.3 now describes the TypeScript-AST scan (fail-closed Vite-order resolution, namespace imports as member access only, the every-code-file boundary check) instead of the old regex/chunk description; the viewer spec's historical "every command is callable from every window" line gets a dated "closed by the AppManifest lockdown" note; the lib.rs doc comment on the_generated_app_manifest_matches_the_handler_list no longer claims independence from the shared parser it actually reuses; and the vitest command-name regex now allows digits, matching Rust's [a-z0-9_]+. Also adds a cargo test backstop (the_tauri_config_capability_check_runs_against_the_real_tree) that runs build.rs's tauri-config capability check against the real app/src-tauri tree on every `cargo test`, closing the gap where a new tauri.<platform>.conf.json on an already-built tree only gets checked by build.rs on a clean build. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-09-22 23:25:50 -07:00
shadowdaoandClaude Opus 5.5	32acdf39fe	docs(acl): revise lockdown spec for the implemented viewer and review rulings ... Five viewer commands (viewer_poll_file was added), both existing census tests, the wrapper-import shape of the frontend, controller rulings on CI scope / Box::leak / webviews, and a spike (§7) that reproduced every mechanism claim against tauri-build 2.6.0 in a throwaway worktree. One design change from the spike: stale autogenerated permissions are pruned selectively rather than by remove_dir_all, because tauri-build emits rerun-if-changed=permissions and wholesale regeneration would rebuild the crate on every cargo invocation. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-09-22 22:12:25 -07:00
shadowdaoandClaude Opus 5.5	508ff6d037	docs: design spec for per-window app-command lockdown via AppManifest ... Follow-up to the terminal file viewer spec. Verified against tauri 2.11.0, tauri-build 2.6.0 and tauri-utils 2.9.0 sources: with no app manifest the ACL skips app commands entirely; with one, every command must be granted to the calling window, unlisted commands are denied, and deny-* is global. The spec derives the manifest from generate_handler! in build.rs and fails the build when a command is missing from, or duplicated across, the capability files. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>	2026-09-22 20:39:38 -07:00