0 Fork 0

mirror of https://github.com/storytold/photocraft.git synced 2026-11-12 05:02:51 +00:00

Files

T

David MannandClaude Opus 5.5 8812fe1e73 Merge main (egui 0.37, #9363 )

Conflicts: the batch's wheel reads (#5547 Animated Zoom) keep their extra
argument with main's ids (`Id::unique`, `ui.scope_id()`); crop presets keep
#6620's `apply_choice` with main's accessible name; Bevel & Emboss keeps
#9370's per-mode id with main's name argument; the Stroke field keeps
#7203's gradients with main's name; tone.rs keeps #9139's move of the
Histogram panel to histogram_panel.rs (main only renamed ids there);
translation catalogs as unions.

Not flagged by git, the batch's new code follows egui 0.37 too: dropdowns
take an accessible name (Histogram Channel/Source #9139, tool Mode #5504,
Art History Style #1610, New Snapshot From #3567), MouseWheel events carry
`source`, `WidgetType` is `Role` (ColorButton is ColorWell, #7203),
`Id::new`/`Ui::id` are `Id::unique`/`Ui::scope_id`.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

2026-10-25 20:53:11 +01:00

architecture

…

automation

fix(cli): help after a mistake, and mcp/serve option notes in --help (#7071 )

2026-10-25 00:08:14 +03:00

development

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

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

formats

Merge PR 1 (codecs, now on current main) into PR 3

2026-10-23 08:48:35 -04:00

getting-started

…

project

…

security

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

2026-10-11 23:18:52 -06:00

README.md

…

SUMMARY.md

…

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.