Files
vangel76 36189363a4 Update stubicc.rs to the reviewed version and record its check
The copy follows storytold/effectcraft#2558: the JSON value is found with white space around the
colon, `\/` escapes and `"` quotes, raw profiles in .aepx hex are replaced, and a profile it
cannot replace stops it before anything is written.

Run over the 17 scrubbed projects before stubbing, the new version writes exactly the 17
submitted files; run over the submitted files, it changes nothing. No fixture changes;
SHA256SUMS is unchanged.
2026-11-04 00:38:19 +01:00
..

AEP generation and inspection tools

The tools that generate and prepare the AEP fixtures. Start with GENERATING.md (generation order, run order, the three preset cases); the cleanup and inspection tools are scrub.py, layers-comps-scrub-aepx.py, patch-text.py, stubicc.rs and inspect-embedded.py with its tests test_inspect_embedded.py (see below).

When contributing them, document:

  • the generation order, authoring application version and required automation interface;
  • original starting projects and media, and the recipes that create them;
  • manual steps and contributor-created presets where automation cannot set a property;
  • removal of identifying metadata and replacement of vendor profile payloads;
  • independent inspection of the resulting files, including raw, base64 and AEPX hex data;
  • the exact commands used to regenerate hashes and run the consuming tests.

The current contributor's generation notes are in EffectCraft's AEP fixture tools. Use that pinned reference as context while preparing a reviewed contribution here. Add the actual tools and required inputs, or identify what remains external or unavailable.

Keep generation notes in docs/aep/, finished fixture payloads in aep/, reviewed presets and starting projects in aep/inputs/, and original media in aep/media/. Configure paths to those inputs explicitly. The earlier scripts' combined/gen/, synthetic/ and presets/ paths describe the contributor's working layout; document how they map to the published inputs and keep temporary generation outputs outside the reviewed collection.

A cleanup tool must not be the sole evidence that its outputs contain no unwanted embedded assets.