0 Fork 0

mirror of https://github.com/storytold/photocraft.git synced 2026-11-14 06:02:48 +00:00

Files

T

dotCooCoo 49d12c57bf Merge main into feat/pcraft-full-composite

# Conflicts:
#	crates/ui-egui/src/i18n/cs.tsv
#	crates/ui-egui/src/i18n/de.tsv
#	crates/ui-egui/src/i18n/el.tsv
#	crates/ui-egui/src/i18n/es.tsv
#	crates/ui-egui/src/i18n/fr.tsv
#	crates/ui-egui/src/i18n/hu.tsv
#	crates/ui-egui/src/i18n/id.tsv
#	crates/ui-egui/src/i18n/it.tsv
#	crates/ui-egui/src/i18n/ja.tsv
#	crates/ui-egui/src/i18n/ko.tsv
#	crates/ui-egui/src/i18n/nl.tsv
#	crates/ui-egui/src/i18n/pl.tsv
#	crates/ui-egui/src/i18n/pt-br.tsv
#	crates/ui-egui/src/i18n/ru.tsv
#	crates/ui-egui/src/i18n/tr.tsv
#	crates/ui-egui/src/i18n/uk.tsv
#	crates/ui-egui/src/i18n/vi.tsv
#	crates/ui-egui/src/i18n/zh-hans.tsv
#	crates/ui-egui/src/i18n/zh-hant.tsv

2026-10-30 06:26:41 -07:00

architecture

…

automation

docs(installer): note that the 32-bit all-users folder is Program Files (x86); tidy wording

2026-10-27 12:25:20 +00:00

development

Security: pin and verify the Windows signing client (#2936 ) (#3938 )

2026-10-25 12:32:10 -04:00

formats

Merge main into feat/pcraft-full-composite

2026-10-30 06:26:41 -07: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

…

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.