mirror of https://github.com/storytold/photocraft.git synced 2026-10-27 03:17:05 -06:00

Files

T

aiongg dfde38919e Merge PR #7883 : Save As JPEG: JPEG Options dialog (quality 0–12, Baseline / Optimized / Progressive) (FILE-215-19)

crates/ui-egui/src/lib.rs: replay_save doc comment names both Export As and JPEG; replay_save uses the PR's FormatChoices::from_step, after main's export_dialog::replay branch.
docs/file-format-parity.md: header keeps main's text plus the JPEG Options item (last updated 2026-10-19); TIFF row is main's, JPEG row is the PR's; change-log rows once each, newest first.
docs/gaps.md: header keeps main's text plus the G10 item (last updated 2026-10-19).

2026-10-22 02:27:46 +00:00

architecture

AF.1: import bounded Affinity previews with fidelity warnings

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

automation

Docs: install the CLI and register it with MCP clients (#7663 )

2026-10-19 13:03:40 -04:00

development

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

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

formats

Merge PR #7883 : Save As JPEG: JPEG Options dialog (quality 0–12, Baseline / Optimized / Progressive) (FILE-215-19)

2026-10-22 02:27:46 +00:00

getting-started

fix(docs): Linux build prerequisites only name Debian packages (#2437 )

2026-10-10 14:35:12 -04:00

project

Progress docs: target-app parity, gaps, alpha gate, readiness by audience (#2696 )

2026-10-10 15:09:04 -04:00

security

Security: harden document exports and automation inputs (#2269 )

2026-10-11 23:18:52 -06: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.