Task: Integrate ERP product search fix

Identity

Integrate source commit b5c727b6f9716243a436a5a0546f3e4db9a95d1d from task 20260902-diagnose-parse-error-7f3a9c2d onto remote main baseline fff9171ba2f08c4638a0753c60a079ec9eccd774.
Keep the source task record on its source branch while merging the product-search implementation, contracts, tests, extension 0.5.165, archive, ZIP, and release manifest.
Promote the verified S_chanpinming search order into canonical current state, business rules, evidence, and rollout memory.
Run the project-document, repository, control-plane, legacy, build, and extension-package checks, then advance origin/main with a normal non-force push and synchronize the local main checkout.

The user explicitly requested that the current product-search changes be merged into main.
Preserve the account-permission UI work already integrated on origin/main; do not merge unrelated feature branches or the superseded recovery checkpoint.
Keep the extension source, platform minimum version, mappings, tests, versioned ZIP, archive, and release manifest synchronized at 0.5.165.
Preserve deterministic unique matching and all existing pre-write failure-closed gates. The live evidence is search-only and must not be represented as an automated selection or ERP write result.
Do not read .env, reload or deploy the extension, restart services, mutate tasks, select products, save ERP forms, or perform any ERP write.
Push only after a fresh fetch proves the remote branch is an ancestor of the fully verified integration tip; never force push.

Integrated source commit b5c727b without conflict through merge commit e4fd916; Git automatically combined its platform minimum-version edit with the account-permission UI baseline.
Kept the source feature task record on its source branch, so this integration changes no other task-owned project document.
Promoted the durable S_chanpinming lookup order and its search-only evidence into canonical current state, business rules, evidence, and rollout commitments while preserving the distinction between read-only search proof and write proof.
The combined integration tree passed all repository, contract, regression, build, and release checks and is ready for a guarded normal push.
A fresh fetch confirmed origin/main was still fff9171; the normal non-force push advanced it to verified integration commit a045701dfcb596df104587212d1b8a755c66ab5a.
No runtime, browser-extension, service, task, or ERP state was changed.

Source ancestry and the source range passed git diff --check before merge.
node --test tools/product-lookup.test.mjs: 11 passed, 0 failed.
node --run check:repo: 10 passed, 0 failed, including exact packaged-extension/source comparison and synchronized release baselines.
node --run check: passed.
node --run test:control-plane: 159 passed, 0 failed.
node --run test:legacy: 268 passed, 0 failed.
node --run build: passed.
dist/ltjt-order-assistant-0.5.165.zip SHA-256 is 14f3150ab26d99131e32321ddc805a85550438bc2810a1e20921f7922b25aaac, exactly matching dist/release-manifest.json.
The temporary node_modules symlink used for isolated-worktree verification was removed.
Fresh pre-push fetch showed divergence 0 3 and proved origin/main was an ancestor of the integration tip. After the normal push, local HEAD, the origin/main tracking ref, and git ls-remote --heads origin main all returned a045701dfcb596df104587212d1b8a755c66ab5a.
This task record is finalized in a documentation-only follow-up commit after that remote-equality check.

Extension reload/deployment and a guarded runtime preflight or retry remain separate, explicitly authorized work.

None. The accepted product-search rule and evidence were promoted by this Integration task.