PolicyWatcher 3.9.0 Beta 41 — Evidence-first AI evaluation and adaptive experience - #7
Merged
Merged
Conversation
| const response = await fetch(url, { | ||
| method: 'POST', | ||
| headers: { 'Content-Type': 'application/json' }, | ||
| body: JSON.stringify(body), |
| expect(existsSync('src/app/api/pulse/launch-kit/route.ts')).toBe(false); | ||
| expect(existsSync('src/app/api/og/launch/[asset]/route.tsx')).toBe(false); | ||
| expect(change).toContain('/api/evidence-packet/${id}?format=pdf'); | ||
| expect(change).not.toContain('/api/report/${change.policy.id}'); |
sev7enITA
marked this pull request as ready for review
August 14, 2026 06:35
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.
What changed
Why
The prior branch and PR names no longer represented the accumulated Beta 41 scope. The AI audit also identified a retired fallback, missing structured-output enforcement, missing evaluation lineage and vulnerable transitive dependencies. This PR consolidates the current evidence-first release on a coherent branch without adopting RAGFlow, LightRAG, Kimi K3 or GraphRAG wholesale.
User and operator impact
AiModelInvocationmigration and requires a verified database backupValidation
npm audit --omit=dev --audit-level=highreported 0 vulnerabilitiesKnown evaluation boundary
Qwen3/BGE and paid Gemini challenger tracks are wired but not represented as completed results because no loopback adapter endpoints or evaluation API key were available. Promotion remains gated on measured golden-set results and human evidence review.