Repository navigation
docs: record real-provider Hybrid ask retest without release promotion - #87
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.
Result
One explicitly authorized real-provider retest after PR #86, using the unchanged 7 fictional documents and 8 fixed cases. All eight flow checks passed: two answer cases, four insufficient-evidence refusals, two no-context cases (empty/deleted). SQL/Chroma and document storage were temporary; JWT, tenant/category scoping, Dense default and typed audit/metrics checks passed in the isolated ASGI app.
Still not release accepted
The NovaVPN 1.0 explicit version constraint is again audited NOT_REQUIRED. The 2.0 mismatch case labels version_and_time SUPPORTED despite acknowledging the source only covers 1.0; other MISSING facets correctly preserve overall refusal. Both semantic warnings remain visible, and frozen v5.3 NO_PROMOTION / FAIL is unchanged. This eight-case flow check is not an independent quality evaluation.
Read-only docker info still fails (dockerDesktopLinuxEngine pipe unavailable). Running-server HTTP, container restart/persistence and rollback acceptance remain unexecuted. Ticket Agent is still Dense, switches stay default-off, no public deployment.
Changes / verification
Only README and a sanitized JSON evidence report. No prompt/rule/code/.env changes, no business documents/TechQA/gold labels/secrets in model input bodies, no ticket creation. No further paid calls.
Complete offline suite rerun: 632 passed in 48.16s with temporary database, dummy credentials and external-socket/private-data guards. Report JSON, executed source SHA256 hashes, per-kind limits, totals, and all eight expected/observed statuses verified; git diff --check passed.