dtourolle/DarkRoom
1
0
Fork 0
Code Issues 39 Pull Requests Actions Packages Projects Releases 20 Wiki Activity

Wrap the three lines that ran past the column the rest of these documents keep

Browse Source 
Prose-only. Three paragraphs added in this branch ran to 105, 113 and 166
columns against a document that wraps at 100 everywhere else, the last because
an edit joined a new sentence onto an existing paragraph's opening line.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
dtourolle
2026-08-30 10:25:57 +02:00
co-authored by Claude Opus 5
parent 6ec6c5cbd6
commit b63ce0290b
2 changed files with 9 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/outstanding.md
+3 -1
View File
@@ -236,7 +236,9 @@ observes that publishing on Play is what turns SAF from a preference into a cons
distribution.md §6 argues the coupling runs the other way for this project — F-Droid asks nothing
that ARCH §6.9 does not already require. Spike S11, the Play permissions dry-run, has not run, and
until it does that argument is reasoned rather than confirmed. Two of the five channels also exist
as decisions rather than as recipes, and no Flatpak has been built here at all. Related, NFR-COMPAT-1's baseline is real but scattered — API 28/36 live in the Android
as decisions rather than as recipes, and no Flatpak has been built here at all.
Related, NFR-COMPAT-1's baseline is real but scattered — API 28/36 live in the Android
Dockerfile and are checked in CI against the built ELF, which is good — while the items the
requirement singles out are missing: whether `shaderFloat16` and 16-bit storage are required (the
one it flags as jeopardising R1), minimum RAM, minimum desktop Mesa, and a named reference device
docs/requirements.md
+6 -5
View File
@@ -74,8 +74,8 @@ results.
**On R5's tiling.** An earlier draft added two clauses to R5's criterion: *"only visible tiles are
computed; panning recomputes only newly exposed tiles"*. They have been struck, and the reason is
the same one that FR-DSP-2 was rewritten for rather than implemented — [frame-budget.md](frame-budget.md)
measured it.
the same one FR-DSP-2 was rewritten for rather than implemented:
[frame-budget.md](frame-budget.md) measured it.
R5's actual demand is met and tested. The display pipeline works at viewport resolution:
`Framing::view` shrinks the sampled region while the render target keeps its size, so zooming raises
@@ -547,9 +547,10 @@ and bit depth are configurable.
**AVIF and JPEG XL are post-v1** and are not part of this requirement's acceptance. Either may still
be listed in the settings page before its encoder exists, on one condition: choosing it shall fail
with a typed error naming the format, never with a file. `every_offered_format_either_encodes_or_explains_itself`
walks every format the page offers and enforces exactly that, so a format cannot be added to the
picker and quietly reach an encoder that does not handle it.
with a typed error naming the format, never with a file. The test
`every_offered_format_either_encodes_or_explains_itself` walks every format the page offers and
enforces exactly that, so a format cannot be added to the picker and quietly reach an encoder that
does not handle it.
*On splitting this requirement.* It read as one undifferentiated list — "JPEG, PNG, TIFF (8 and
16-bit), and AVIF or JPEG XL" — which left it neither met nor unmet. Three formats, both TIFF