{"version":"2.1.269","anchor":"context-hook-validation-simplified-attachment-lineage-check","canonical_anchor":"context-hook-validation-simplified-attachment-lineage-check","heading":"Context-hook validation simplified: attachment-lineage check removed","tier":"internal","area":"Plugin Hooks","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/context-hook-validation-simplified-attachment-lineage-check","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Context-hook validation simplified: attachment-lineage check removed\n\nHook-provided context entries no longer need to trace back to an earlier hook that added them\n\n**What**\n\nHooks (scripts that run at certain points and can attach extra 'context' information) previously had their context arrays checked to ensure every entry could be traced back to something a prior hook in the chain had actually added. That lineage check has been removed. The validation now only checks that context values aren't non-list, that entries aren't empty strings, and that the total length doesn't exceed the character limit.\n\n**Why**\n\nThis loosens what hook-supplied context is allowed to look like, dropping a rule that previously required an unbroken chain of attribution between hooks; the practical effect is that a hook's context is no longer rejected purely for not matching what an earlier hook passed along.\n\n- Area: Plugin Hooks\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}