Clarify fixture capture limits and final analyzer evidence

This commit is contained in:
2026-11-07 19:57:49 +00:00
parent b82e89f66f
commit 5ddd52f817
+9 -1
View File
@@ -38,7 +38,7 @@ Validation:
111s, /tmp/memwatch/out.4le2Y1.
- Final deck geometry/fill plus preview regression: 64 passed,
/tmp/memwatch/out.BMiUMQ. Analyzer clean (flutter-analyze.GvPMna before the
small final geometry polish; final analyzer recorded in deployment evidence).
small final geometry polish; final analyzer is clean, flutter-analyze.UtY2Ce).
- Browser captures /tmp/review/settings-library-films-fixed record all eleven
previews plus all Settings categories; reviewed every preview sheet.
- Material dark phone and Cupertino light phone/desktop Settings reviewed in
@@ -55,3 +55,11 @@ Validation:
animation evidence. Obsolete fixture-title attempts also remain identified.
- No connected Android test device; managed AVD data is missing. No device was
created and the personal Fold was not used. Publication is not installation.
Capture limits: the generic full-app fixture does not answer notification_settings,
so the Notifications screenshot shows that explicit fixture error; the fixture
also has no served APK version bundle, so Updates shows its empty-download state.
Those are not captures of populated live notification settings or release-update
metadata. Dedicated settings/application tests cover the controls and lazy fetch;
public release bytes/signature are verified separately. No production settings
were changed to populate screenshots.