[ZacxDev]

What

civitai app validate now reports the two reserved storage collection fields, registry and hook, as "not available yet". civitai.com refuses both at submit while registryExport and hooks are off in civitai main's APP_STORAGE_ENABLED_FEATURES.

They use the same path as the five existing gates (kind "log", write "anyone"/"owner", ttlSeconds, dailyWritesPerAuthor): a warning from storageFeatureGateWarnings, built by storageNotYet from the server's notYet text plus the CLI's "refuses this at submit today" suffix, and located at the field.

What an author sees:

storage.collections.<name>.registry is not available yet — collections published to registries arrive in a later phase of App Storage; remove it to keep the collection on Civitai only. civitai.com refuses this at submit today; …
storage.collections.<name>.hook is not available yet — permission hooks arrive in a later phase of App Storage; remove hook (the collection schema still applies). civitai.com refuses this at submit today; …

Order of checks (matches parseCollection)

• registry: the server checks the feature switch before it checks the value or the shared-only rule, so any declared registry gets the gate.
• hook: the server checks the switch only after parseHook accepts the shape. hookShapeAccepted copies the shape checks the schema states (allowed keys, file pattern and length, no node_modules, sha256 pattern, timeoutMs 1 to 500). A malformed hook gets the schema's error and no gate.
• One known difference, documented in the code: the server's rule against a file inside outputDir is not copied. A hook there gets the gate warning here, where the server names outputDir.

There is no hook behaviour: no file is read and no digest is checked.

Tests

• TestStorageFeaturesNotYetAvailableAreWarnings/{registry,hook}: each declared field gets exactly one gate warning with the exact text and field, and no error. A twin collection without the field gets nothing.
• TestVendoredSchemaStillStatesTheFeatureGates: rows for both RESERVED schema sentences, so the gate list matches the schema.
• TestStorageFeatureGateOrderMirrorsTheServer: six malformed-hook rows that get the schema error and never the gate.
• Both fields are added to the finding-field ledger and the contract corpus.

Dependency

This needs #887, the re-vendored schema that adds registry and hook. Until #887 merges and this branch is rebased, the new rows fail on this branch because the vendored schema still rejects both fields as unknown properties.

🤖 Generated with Claude Code

[ZacxDev]

Audit at f44232bdc4.

• Round 0 (requirements and deletion): proceed to the checklist.
  • D1 kept. hookShapeAccepted copies the schema's hook rules, the same way this file already copies the ttlSeconds bounds.
• Round 1 (full checklist): no 🔴 and no 🟡, so the audit ladder ends here.
• 🟢 1 and 🟢 2 are closed in c97edfff. The five surviving mutants each have a row now.
  • Each row went red under its mutant in CI run 42882896990.
  • The revert keeps tree 08ed5276.
• 🟢 3 stays open. The server also refuses a hook file inside outputDir, and the CLI does not copy that rule. Closing condition: the PR that removes the hook warning once APP_STORAGE_ENABLED_FEATURES.hooks is true also ports that rule.

D1 — replace hookShapeAccepted's copy of the schema's hook rules with "hook declared and no schema error under storage.collections.<n>.hook" (reuse hasFindingUnder), removing a second copy of the schema's rules

1. test rows pin a 200-character file, a .mjs file, timeoutMs 0, a missing sha256, and the registry gate on a private collection