Repository navigation
Conversation
chore(deps): integrate dependency upgrades on patched backend stack
chore(deps): integrate secure dependencies and shared CI coverage
DavidHLP
changed the title
fix: request JSON decisions and retain sealed acceptance history
fix: reject invalidated draft confirmations with conflict
…tion fix: retain sealed V15 costs for confirmation revalidation
fix: retain safe U03 cancellation failure diagnostics
fix: retain sealed V16 costs for cancellation revalidation
fix: recognize equivalent array range adjective definitions
fix: retain sealed V17 liabilities for array range acceptance
fix: reconcile interrupted save intent as unknown
fix: preserve sealed recovery acceptance accounting
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
1 participant
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.
U03 previously inferred
business_rows=1from HTTP receipts. The acceptance driver now reads the LearningPlan owner's database in a read-only transaction and binds the authenticated owner and stable business key: zero rows before the first write and one matching row afterward. Crash-before-HTTP recovery must retain zero rows. Existing repeated, concurrent, conflicting, receipted-recovery, confirmation-invalidation and cancellation checks remain required.The integrated branch also includes dependency/security repairs, provider-output parsing and bounded boundary-evaluation corrections, plus immutable V13–V18 revalidation history bindings. Every failed predecessor record, known charge, conservative commitment and the three historical unknown-usage liabilities remain retained. No ledger reset, automatic paid retry, relaxed acceptance criterion or replacement receipt is implied.
Current integration head:
710f9126edf3be3d243f9e75c69680c43ecd7bcc. Its Git tree equals reviewed save-intent recovery candidate50d720ad10153bcb83d90c6d79a2259cccf28c34; exact repair-candidate CI 38156569344 succeeded, and remote full Agent checks passed 1719 tests, with one optional Qdrant dependency skip, exit 0. Original genuine-model receipts remain bound to execution candidate3730b74140a107265d0cebc44a988c644bbc45e7, whose earlier CI38151314096 and1718-test results remain historical. These checks do not establish genuine cross-service acceptance for the changed candidate.V18's real source analysis, three citation probes and both complete 20-case development passes finished. Zero-call strict replay verified all 80 development provider exchanges, exact answer/judge prompts, returned answers, classifications and known usage; both passes contain 20 completed behavior matches and no unsupported citations. The six-category boundary batch passed all six behaviors with 12 calls, and dual-account isolation passed its HTTP controls and three model scenarios with seven calls. Their strict formal component validators passed. Two preceding boundary parameter preflight rejections made zero model calls and remain retained.
The complete U02 gate passed, including strict readback, on original execution candidate
3730b74140a107265d0cebc44a988c644bbc45e7; gate SHA256e740b06a7bced6c9ef2cc5159c23b494cb59f8f2bf61af7334d552d76ecd550d. Its five canonical evidence items, original provider exchanges and continuous 103-attempt budget chain were verified, with 35,582 microUSD known actual usage and no new unresolved usage. Vector comparison preserves historical Qdrant execution provenance with current dependency equivalence; historical holdout/holdout2 exposure remains recorded. This does not claim fresh Qdrant execution or unseen quality.This PR remains Draft. The original real U03 batch terminated INCOMPLETE, exit1,
u03_restart_status_mismatch: six preliminary idempotency/ownership/confirmation/cancellation scenarios passed, but restart before Java save dispatch returnedsavinginstead of the requiredunknown. PR284 repaired that recovery branch and merged into this integration head. The original failed record and all104 V18 calls remain permanently sealed, not relabeled. PR285 added reviewed V19 immutable accounting for a fresh acceptance prefix with unchanged cumulative USD200 and purpose/token limits; candidatefa729d255 passed1732 remote Agent tests/1 optional Qdrant skip, two reviews, and all CI38157973770 jobs, then merged as2fb129404866f077abc93facc4540180b270a52b. V19 was verified against57 historical files and activated at zero calls. Its new source/citation prefix passed4 calls/723 microUSD. First fresh20-case development pass completed20/20 behavior matches/40 calls; the second20-case pass is currently running. U03 final acceptance and frozen U04 holdout/reliability acceptance remain incomplete. Historical U02, tests and tree equivalence do not substitute for those gates. Private accounting, raw answers, credentials and sealed holdout contents remain outside the public repository.