mirror of https://github.com/storytold/photocraft.git synced 2026-10-28 10:11:58 +01:00

Files

T

callmeBallochandClaude 57ae2fb1a3 Merge storytold/main into AF.3 native Affinity import

Conflicts: File › Open and batch extension lists (SVG, swatches and
Affinity together); the import dispatcher (upstream's type-layer
preparation with the new result fields); the pinned EXR and Affinity
corpora side by side; README, book and development docs.

Affinity type layers now draw through text_import::prepare, so they get
the same raster bound as other imported type, and SVG import fills the
two new ImportResult fields.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01GQPh8UDgMyARR5Hat9UchC

2026-10-09 04:26:18 +00:00

architecture

AF.1: import bounded Affinity previews with fidelity warnings

2026-10-08 17:42:23 +02:00

automation

fix(cli): report missing font fallbacks in run, info and convert (#1299 )

2026-10-08 16:08:50 -04:00

development

docs: add mdBook and security documentation foundation (#35 )

2026-10-04 12:31:18 -04:00

formats

Merge storytold/main into AF.3 native Affinity import

2026-10-09 04:26:18 +00:00

getting-started

docs: add mdBook and security documentation foundation (#35 )

2026-10-04 12:31:18 -04:00

project

docs: add mdBook and security documentation foundation (#35 )

2026-10-04 12:31:18 -04:00

security

Automation: an allowed command can't run a denied one on its behalf (#861 )

2026-10-07 23:58:26 -07:00

README.md

docs: add mdBook and security documentation foundation (#35 )

2026-10-04 12:31:18 -04:00

SUMMARY.md

Merge storytold/main into AF.3 native Affinity import

2026-10-09 04:26:18 +00:00

README.md

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.md for repository rules and verification gates.
README.md for 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.