Repository navigation
[INBOX/OSS][P1] CodeScanner 2.5.2:真正可用的摄像头二维码扫描 + 离线文本交换 - #81
Draft
Righteous1776 wants to merge 12 commits into
Draft
Righteous1776 wants to merge 12 commits into
Righteous1776 wants to merge 12 commits into
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.
A practical, narrow, third-party OSS intake — not feature-count inflation
Current VeilLink main
501ef814a0a9bea41419fe2d9f48315371b30320has remote pairing QR generation and photo-import only, and the Tool Center's local QR generator has no scanning. This Inbox contains a real integration patch adding camera QR scanning in both locations.Inbox:
AGENT_INBOX/submissions/oss-integration-agent/20261025-codescanner-practical-qr/Actual code delivered
FILES/VeilQRScanPolicy.swift: testable Foundation-only input validation (1024-byte offline text, 4096-byte remote QR, control-character filtering andveillink://pair?scheme preflight).FILES/VeilCameraQRScannerView.swift: single-shot CodeScanner SwiftUI camera sheet, bounded QR text only, no background capture, no photo capture, no data exfiltration, no auto-opening.FILES/VeilQRScanPolicyTests.swift: five iOS XCTest cases staged.PATCH.diff: exact main four-file update — XcodeGen Swift package pinnedexactVersion: 2.5.2, truthfulNSCameraUsageDescription, add camera button to remote one-minute QR pairing (still Relay-dependent), and camera button to existing temporary offline QR text generator. Photo picker remains unchanged.OSS_PRIORITY_MATRIX.mdevaluates nine legitimate upstream packages including CodeScanner, Mantis cropping, SwiftSoup local HTML, MarkdownUI, Nuke, Kingfisher, ZIPFoundation and GRDB with toolchain/platform/license constraints.Verified: Official CodeScanner 2.5.2
Package.swiftdeclares Swift tools 5.9/iOS13/zero deps; MIT upstream. Currentproject.ymlis Swift 5.9/iOS15. In-memory reapplication of all 9/9 unified hunks on exact GitHub main passes original context checks. Standalone Foundation QR policy Linux swiftc 6.2.1 Swift-5 mode with warnings-as-errors passed 10 functional assertions. Bundled iOS XCTest not yet executed, and Apple SDK/physical iPhone7 has not been compiled/tested. No third-party code copied, only pinned dependency declarations.Security: Remote pairing uses existing
VeilRemotePairingCoordinator.consumeQRCodeso original QR expiry/crypto/6-digit mutual confirmation stay in force; scanning does not make remote Relay pairing work offline. General QR text scan is offline, with URLs opaque and no auto-open. No Keychain, DB, protocol, signing or BLE changes.Overlap / hard gates: Shared
ToolCenterView.swiftalso touched by Inbox PRs #67/#68/#70/#72/#76. Governor must resolve addition without overwriting others, and prioritize iPhone7 touch/startup P0 PR #64/#65/#66. Requires macOS iOS15 build, full XCTest, physical iPhone7 camera permission/focus/light-dark/gesture tests, and third-party license attribution. This PR is INBOX ONLY: no main merge, no workflow dispatch, no IPA/release.