Repository navigation
chore: refresh toolchain and fix capability and CI checks - #144
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Contributor
Browser QA (agent-browser)
|
This was referenced Oct 11, 2026
This branch was successfully deployed
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.
Changes
Source and capability corrections
Current head:
5236e3b53b050d25a5da6eb069fe3e82fb2b48af. Incremental bug-slice base:b0fbed357b967921ad0be58e44742fd136a48e2d. Bothb0fbed357..64b4a92and64b4a92..5236e3bcleared by coordinator review: NO ACTIONABLE FINDINGS; receipts held centrally.bfrom byteB; MBps/GBps are not misread as bit rates.Verification
Credential blocker resolved on the same reviewed head. The new key was added to Convex project defaults, which do not update existing previews. Redeployed without source changes; fresh Vercel preview is Ready and uses new backend
usable-grasshopper-38in slot16. Vercel metadata confirms SHA5236e3b53b050d25a5da6eb069fe3e82fb2b48af, Bun1.4.2 and Node24.21.0. No key was read or printed.Fresh preview validation passed: seed8/8 products,38 rows, manual inference (USB-C/USB-C, >=240W, high-speed data), and hosted browser inference/edit/reset. Downloaded artifacts show no console/page errors; inference screenshot inspected. Browser replay from the first successful validation. Required Check gates remain intact; stale failed gate runs are being refreshed against the successful preview. Coordinator retains merge/production ownership; no auto-merge.
Backfill impact: future authorized ingestion receives the corrected fields. Existing stored rows were not inspected, mutated or replayed; this PR does not repair historical catalog data. Any backfill needs separate authorization and verification. The full provider-backed ingest integration suite and production validation remain unverified; bounded hosted inference/browser validation now passed.
Data Quality Grade: B for the bounded source corrections; overall PR remains C. Vendor payload comparisons, source URL/timestamp, preserved identifiers and unit-aware/tri-state behavioral tests support this slice. Negation recognition is deliberately limited to explicit incompatibility/non-support phrases, not general NLP. Unexpected fixture requests fail, and live drift fails assertions rather than skipping them. No credentials, production resources or gate semantics changed.
Coordinator owns the cleared review receipts, credential unblock, eventual merge and production verification; close superseded dependency PRs only after merge. Full consumer trace, red/green and current CI evidence are in
.memory/fleet-maintenance/b8173-findings.mdandhandoff.json. The implementation worktree is preserved for resumed credential validation.