Release 0.8.0: remediation threads, GitLab commands, and docs - #122
Merged
Conversation
This was referenced Aug 22, 2026
7 tasks
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.
Release target
e2c5b847a3884edeeeb24123412af51b280faf14cec4be33c6fff27de93fded041cde06a798d1ca7Added
ocr.review-context-policy/v2with optionalremediation_threads; policy v1 remains accepted for existing discussion/reference configurations.ocr.context-store/v2remediation records and read-onlyremediation_threadprojections throughcontext_listandcontext_get.@<live-bot-username> suppressand@<live-bot-username> resolve, with slash-command parity.OCR_MAX_TOOLSwith OCR 1.9.10's default of 30, plus explicit local-only private-artifact retention for DLP diagnosis; validated GitLab MR execution rejects retention.Changed
GET /user; verified remediation roots require the live bot ID and toolkit marker/fingerprint.review --preview; the toolkit does not configure or duplicate OCR thresholds.Removed and migration
OCR_GITLAB_BOT_USER_ID; authenticatedGET /useris authoritative.OCR_USE_ANTHROPIC; setOCR_LLM_PROTOCOL=anthropic.OCR_RUN_HELPER_TESTSand unsupported documentation-onlyOCR_LLM_SUPPORTS_FUNCTION_CALLING,OCR_LLM_SUPPORTS_REASONING, andOCR_CONFIG_PATH.@bot retestremains out of scope because the CI-only toolkit has no GitLab Note Hook receiver; use GitLab retry UI/API.OCR compatibility
OCR 1.9.9 — inherited predecessor
OCR 1.9.9 was qualified with toolkit 0.7.1 and remains historical evidence only.
OCR 1.9.10 — exact 0.8.0 target
359e5bafda1438a47ef389399f4994350e1016371eac1dc17a2c428acb228e6c.Exact-head validation
e2c5b847: Python 3.12–3.14, macOS/Linux, build, dependency audit/review, Bandit, Gitleaks, and CodeQL.git diff --checkpass.6bc46d424b5ca4cb412134607a28e8683aabda70cceb85d3bddca68d44167c05; sdist225ecf88fddfe23be503de109dfe9e9b8b354c815e22e75c1e29613fa5208cca.OCR review and explicit waiver
The final direct OCR 1.9.10 review completed all 43 selected files at concurrency 2 and
--max-tools 60, with no failed, reused, or waived files and no tool-round exhaustion. Static validation and self-review reduced its candidates to five confirmed bounded corrections, all covered by regressions and the gates above.The separately planned enriched-context receipt was not produced. On 2026-08-24 the owner explicitly waived that remaining qualification and requested no further qualification run. Therefore this PR does not claim external receipt evidence for actual
context_list/context_getuse, still-present/evidence-resolved model behavior, or the receipt-level leakage audit. The waiver removes that plan-specific blocker; it does not replace deterministic tests, direct OCR remediation review, exact-head hosted checks, or the stable-release registry/provenance/readback gates.Closes no issues yet. Coordinates #120, #126, and #127; they remain open through stable external reconciliation.