Bring the wiki back in line with the code
Last touched before the production-readiness pass, so several pages
described code that no longer exists.
Technical-Details:
- Dropped the "Metadata Preservation" patch section. That patch was removed
when the SDK moved to Ramses-Py d19ce44, which fixes the defect upstream.
Renumbered the rest and added a short note on why a patch gets deleted
rather than left in place once upstream catches up.
- "Dry Path Resolution" described patched path-resolution methods. It is
actually a permanently-installed os.makedirs wrapper plus the
DisableMakedirs context manager, and the flag is thread-local for a
reason worth stating.
- Render verification described a glob search. That was replaced: a glob
star also matched things like SH010.preview.exr. It is now an anchored
\d+ pattern over a single os.scandir pass, and it checks the frame COUNT
rather than the existence of some frame, which is the part that actually
catches a render that died halfway. Documented the -1000000000 unset-range
sentinel too, since a naive reading of COMPN_RenderStart would fail every
render on a comp without an explicit range.
- Documented the validation repair keys and the re-check after repairing.
Developer-Guide:
- Test count was 121, now 244.
- Project structure was missing asset_browser, ramses_patches and the
vendored deps.
- Same stale patch list as above.
- Added the three ways to run the suite and why each matters. This is not
theoretical: the runners order test classes differently, and a test that
replaced a module attribute without restoring it broke a later test under
unittest while staying green under pytest.
- Added the persistent-interpreter restart rule and a note that some
questions need a probe run inside Fusion, not reasoning about the API.
User-Guide:
- Publish is now five steps: validation and render verification were
missing. The backup is numbered, not timestamped.
- Documented the Fix It / checkbox repairs.
- Documented the vertical/horizontal layout toggle.
Troubleshooting:
- Added the incomplete-render abort, the validation stop, and the
restart-Fusion-after-an-update case.
Docs: Standby shots stay visible, shot claiming, per-deliverable import
Bring the artist-facing pages in line with recent behavior:
- Switch Shot "Smart Filtering": the list now skips only "Nothing to do"
shots; Standby (including freshly-added, not-yet-started shots) stays
visible. The old text said Standby was hidden, which was the opposite of
current behavior and could make new work look missing.
- Document shot claiming: creating a new shot auto-assigns it to you when it
is unassigned (never overrides a lead's assignment), and the feedback line
shows an amber "assigned to <name>" reminder when you work on someone
else's shot.
- Import Published now lists one row per deliverable within a published
version (footage and a .comp shown separately and independently
selectable). Recognized types come from how Fusion is registered as an
application on the step, not a hard-coded list; sidecars and previews are
never listed.
Document the Open Preview side-button in Review & Publish
Wiki accuracy pass
- Assets and Loaders: outdated-Loader detection section, .comp merge
note, Smart Update mention
- User Guide: preview destination, .comp merge, orange Loader hint
- Technical Details: Saver sequence-start management under anchors
- Home: client-ready deliverables feature bullet
- Developer Guide: current test count (121)