Repository navigation
feat: ship qualified source-state solution playbooks - #75
Merged
Merged
Conversation
added 30 commits
October 24, 2026 23:26
…ok-qualification # Conflicts: # .agents/skills/validate-sas-release/SKILL.md # docs/PLAYBOOK-RUNTIME-QUALIFICATION.md # scripts/run-playbook.ts
…ok-qualification # Conflicts: # .agents/skills/validate-sas-release/SKILL.md # scripts/run-playbook.ts
added 16 commits
October 25, 2026 05:24
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.
The four business solution graphs previously depended on generated drafts that could invent verification, misassign owners or omit financial exceptions. They now execute packaged source-state preparation tools: pinned Jev interpretation selects source facts, code performs exact arithmetic and bounded XML parsing, and each phase retains source evidence, probabilities and pending human authority.
The same 72 original adversarial cases and thresholds remain mandatory. The final immutable 0.1.31 cohort passed all 72 primary reviews and strict provider/parser/stage reconstruction. Finance, supplier selection, security preparation and Brazil reconciliation each passed 18/18 with zero high/critical failures. Qualified execution is restricted to Jev1.14.0 and the exact packaged Node/runtime; Brazil additionally pins Python/Expat. The MLX server was harness-only and is not qualified. No Lovable inference was consumed. Earlier rejected histories remain separate.
Adds source-bound registry preparation and anonymous ZIP/publication verification. All four exact archives were imported without overwriting old versions and published through the authenticated admin review flow. The public package API now selects the registry's exact latest version and exposes recorded compatibility only when source/archive/protocol, actual reviewed outcomes and severity scores agree; package contents remain immutable.
Validation: 331 tests and all 12 project checks passed, including strict lint, build, generated content, navigation, RLS and anonymous-access checks across 92 tables with unchanged allowlists. Independent parser/provider/CLI and stale/partial/model/version substitution regressions are included. The live pre-fix public check reproduced missing compatibility in all four packages; post-deployment HTTP/ZIP verification remains required. Publication tooling never changes reviewer/publication flags. This PR does not activate the separate, unqualified Agent Match Jev candidate.