From 49369a1253cf991d2d6d43f9d009d3f0cda2f704 Mon Sep 17 00:00:00 2001 From: Josh Wulf Date: Thu, 21 May 2026 16:31:55 +1200 Subject: [PATCH 1/2] feat: suppress feature specs covered by scenario-template ontology MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit For every Invoke/Observe step in a scenario-template instantiation (EdgeLifecycle, EntityLifecycle, UpdatedFieldVisibleOnReadBack, StateTransitionVisibleAfterAction) the materializer now omits the per-endpoint feature spec for the operationId those steps target. The lifecycle spec is the canonical functional test for those operations; emitting a parallel feature spec is either strictly weaker (EntityLifecycle case) or structurally malformed (EdgeLifecycle case: a key-only prereq chain cannot encode the establish-before-revoke precondition). The behaviour is template-agnostic and coverage-driven, not hard-coded: - New module `materializer/src/coverage.ts` walks the on-disk template scenario JSONs under `generated//scenarios/templates/