onlyworlds 0.43.1

• Schema repinned to schema-dist v0.33.0-dist.54 (from dist.49; same canonical 00.33.00, no schema file moved, so _schema.py moves its provenance lines only: SCHEMA_DIST_TAG, SCHEMA_DIST_SERIAL 54, SCHEMA_MANIFEST_SHA256). Five serials in the vendored tree: 50 and 51, example/world-export.json's world block is the World whole, with origin and x_names (keel #516, #571); 52, profiles/review.md's reader rule (a reader that hands a world on leaves proposed elements out unless asked); 53, the folder lint (walk/lint_folder.py) takes hidden as a folder key, true or false (folder spec §4.8), and review.md's rule 4 on a malformed mark; 54, profiles/checks.md's where.type as a list and reader rules 6 to 8 (a known-of stub judged by no rule, a pattern outside the shared subset not checked by name, the size cap no step limit), and checks.fixture.json's rule 6 with four cases and three not-checked rows. The doctor already reads all of it: the fixture replays clean (7 rules, 17 cases, 39 expectations, 11 not-checked rows). Tree from git archive of the tag (commit 6153745); MANIFEST sha256 82ba25c1... matched against the raw file GitHub serves at the tag. FORMAT_VERSION stays 0.3.18: the dist carries no folder-format stamp, and the package's moved by hand in 0.42.0. No API change.
• apply_checks judges no known-of stub itself (the checks profile's rule 6, dist.54): a stub is neither scoped nor short. Until now only the doctor left stubs out before calling it, so a direct caller passing a guest's stubs got them reported short on fields that are unknown, not empty.
• Tests: the door tests' lint checks (LegendKeeper's API and file roads, Kanka, World Anvil) tolerated one "hidden is not a field of" line per hidden element while the lint did not know the mark; now that it does, any lint line fails them (test_folder_lint_passes_with_the_hidden_mark, renamed from ..._but_for_the_hidden_mark, in three files; lint_ok and hidden_lint_ok), each watched failing against dist.49's lint. The doctor's checks tests hold dist.54's counts as their floor and require the fixture's null-reason control row, so the not-checked comparison runs both ways.