mirror of
https://github.com/storytold/photocraft.git
synced 2026-10-24 09:57:08 -06:00
skylar taylor-barrick
61b6276c78
* chore: clear strict Clippy simplifications * security: harden web exports and generated image assets * security: reject redirected directory bundle writes * security: quote paths in droplet shell launchers * security: use private ephemeral print spool files * security: bound automation file reads and MCP input * security: bound MCP transport requests before dispatch * chore: keep current sample checks Clippy clean * security: preserve safe export roots and print semantics * security: clear non-sending print state before replay * security: forget print send overrides between jobs * chore: keep macOS UI tests and Clippy clean * Test web export paths portably on Windows
PhotoCraft Documentation
PhotoCraft is a native image editor written in Rust. This book is the maintained entry point for installation, architecture, formats, automation, development, and security documentation.
The repository's existing docs/ directory remains authoritative for detailed design notes, parity reports, UI conventions, release procedures, and the complete control-protocol method reference. The book links to those documents instead of copying them.
Start here
- Users and evaluators: Installation
- Contributors: Building and Contributing
- Architecture work: Architecture overview
- Agents and automation clients: Automation overview
- Security-sensitive work: Security overview and Threat model
Documentation for coding agents
Coding agents should read the following in order:
AGENTS.mdfor repository rules and verification gates.README.mdfor product scope and current entry points.book/src/architecture/for crate boundaries and command flow.book/src/automation/before driving the CLI, control protocol, or MCP server.book/src/security/before changing a parser, file I/O, automation, MCP, the control server, command execution, or serialization/deserialization.
Agents must treat document bytes, paths, command parameters, and automation messages as untrusted input. A page that describes a proposed control does not mean that control is implemented.
Status language
Security pages use four labels consistently:
- Implemented: behavior confirmed in current source or tests.
- Known limitation: an exposed risk or missing control in current source.
- Proposed: a design direction that is not enforced by the current build.
- Future hardening: useful follow-up work without an accepted implementation yet.