Repository navigation
Fix Workflow Index purity failure from naming bootstrap classification - #744
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem and change
DGX's deferred workflow registry fails strict parity with
workflow_purity_regression: the naming workflow added in #645 uses the standard startup seed bootstrap, but its bootstrap module was omitted from the explicit seed-support paths. All 109 live workflows were represented and graph-complete; the sole blocking counter was this path misclassification.Recognise only the conversation-naming bootstrap module. Runtime naming still resolves the published Vontology graph. The zero-failure baseline, strict policy, and runtime seed-import checks are unchanged. A negative test keeps a runtime naming service outside the permitted paths; the naming bootstrap test now proves a customised live prompt survives and the existing graph is not republished.
Validation and release decision
60 targeted tests passed across naming, seed authority, purity reports and registry parity (one new fixture-path error corrected and its suite rerun). Static purity reports zero blocking increases; existing line-count advisories remain visible.
git diff --checkpasses. Merge decision changes: ready for this bounded Tier 1 correction; live deployment acceptance will require parity read-back, index readiness and a representative discovery query.Native task: #V#task_agent_ae643ee9655b975a171b94478b450119. No federation/import changes or baseline refresh. Separate missing testing-substrate types observed in operator diagnostics are outside this fix.