Surfaced by the new hydra gate-30 (effective-manifest cross-reference) fleet dry-run — 2026-07-06 manifest audit item 19 (hydra PR #83).
Finding (hard errors, exit 1): src/manifest.json binds several detail/index pages + sidebar/props widgets to OpenRegister schemas that are not declared as schema keys in lib/Settings/shillinq_register.json or any lib/Settings/register.d/*.json fragment:
Kostenpost (8+ manifest refs — pages ~97, WBSO/RDS surfaces)VATAuditRecord (pages 117, 118 + sidebar audit-records widget)VATGLAccounts (page 118 sidebar gl-balances widget)WBSOTag (pages 185, 186)WBSOActivityCode (page 187)
These names DO appear in the register JSON — but only inside description prose and x-openregister-calculations formulas (e.g. sum(Kostenpost.amount, filter…)), never as an actual components.schemas key. So the manifest (and the calc engine) reference schemas the register never defines.
Impact: same failure class as the zaakafhandelapp besluit/resultaat 404s the audit e2e caught — the index/detail pages and their widgets will 404 against OpenRegister at runtime (the object endpoints dont exist), rendering empty/error states. Because shillinq declares its registers in-repo, gate-30 treats this as a blocking error rather than a WARN.
Fix options: (a) add the missing schemas to shillinq_register.json / a register.d fragment (if these WBSO/VAT/cost-center features are real and intended), or (b) remove the orphan manifest pages/widgets if the features were never built. The calc formulas referencing Kostenpost.amount etc. suggest (a) — the schemas were designed but never declared.
Once gate-30 (#83) merges it will flag this on any PR touching these manifest/register files. Ref: apps-extra/MANIFEST-AUDIT-2026-07-06.md item 19.
Gemigreerd van Codeberg — oorspronkelijk Conduction/shillinq#368, geopend door rubenvdlinde op 2026-07-06.
Surfaced by the new hydra gate-30 (effective-manifest cross-reference) fleet dry-run — 2026-07-06 manifest audit item 19 (hydra PR #83).
Finding (hard errors, exit 1):
src/manifest.jsonbinds several detail/index pages + sidebar/props widgets to OpenRegister schemas that are not declared as schema keys inlib/Settings/shillinq_register.jsonor anylib/Settings/register.d/*.jsonfragment:Kostenpost(8+ manifest refs — pages ~97, WBSO/RDS surfaces)VATAuditRecord(pages 117, 118 + sidebar audit-records widget)VATGLAccounts(page 118 sidebar gl-balances widget)WBSOTag(pages 185, 186)WBSOActivityCode(page 187)These names DO appear in the register JSON — but only inside
descriptionprose andx-openregister-calculationsformulas (e.g.sum(Kostenpost.amount, filter…)), never as an actualcomponents.schemaskey. So the manifest (and the calc engine) reference schemas the register never defines.Impact: same failure class as the zaakafhandelapp besluit/resultaat 404s the audit e2e caught — the index/detail pages and their widgets will 404 against OpenRegister at runtime (the object endpoints dont exist), rendering empty/error states. Because shillinq declares its registers in-repo, gate-30 treats this as a blocking error rather than a WARN.
Fix options: (a) add the missing schemas to
shillinq_register.json/ aregister.dfragment (if these WBSO/VAT/cost-center features are real and intended), or (b) remove the orphan manifest pages/widgets if the features were never built. The calc formulas referencingKostenpost.amountetc. suggest (a) — the schemas were designed but never declared.Once gate-30 (#83) merges it will flag this on any PR touching these manifest/register files. Ref: apps-extra/MANIFEST-AUDIT-2026-07-06.md item 19.
Gemigreerd van Codeberg — oorspronkelijk Conduction/shillinq#368, geopend door
rubenvdlindeop 2026-07-06.