[Seungpyo1007]

What & why

The user asked to keep collection and verification, with as few comments as possible: either a PR generator, or one final verification comment and nothing more. This PR does both.

Collection becomes a manual PR generator. collect.yml:

• It is workflow_dispatch only and runs on develop only. It calls one of TechEngine's reusable workflows, pinned by SHA: ingest (category, limit, include_drafts), refresh (sleep), or promote (apply, max_urls, max_wikidata, max_crossref).
• Each task keeps at most one open PR into develop, on a fixed branch: collect/ingest-<category>, collect/refresh or collect/promote. Every run force-pushes that branch and edits the PR body in place. If nothing changed, no PR is opened.
• The PR comes from github-actions[bot], using this repository's GITHUB_TOKEN. No personal or bot-account token is involved, nothing runs on a schedule, and nothing posts comments.
• That PR starts no other workflow, so the collector runs app.validate and integrity_check.py --strict before it pushes. The result and the Tier 0 report go in the PR body, which is capped below GitHub's limit and scrubbed so it can't mention anyone.
• The collector sets the sidebar itself: assignees, data and enhancement, the Massive milestone, and Closes #295/#296.

Verification goes into the one final-check comment. When a maintainer adds final-check, the check job now also runs python -m app.verify pr --base <base>:

• Tier 0 scores the changed records.
• Tier 1 checks their source URLs and Tier 2 cross-references them on Wikidata, for at most 40 records, with the engine's TechEngine-verify User-Agent.
• Tier 3 is a dry run that writes nothing.

The report goes into TechEngineBot's single comment under a <details> block. @ is removed, and a zero-width space breaks #123, GH-123 and links, so the comment can't mention anyone or cross-reference an issue. It is informational: the pass/fail verdict still comes from the build.

Engine pin. TechEngine moves from 5577b3f to 3c50cb8 (TechEngine main):

• fix: honest crawler User-Agent; collection as manual PR generators TechEngine#127: crawlers send TechEngine-verify/0.1 (+https://github.com/GetTechAPI/TechEngine) instead of a Chrome User-Agent. An anti-bot challenge counts as "unknown" and can no longer promote a record. The DuckDuckGo and Bing scraping is gone. ingest, refresh and verify-promote became the reusable PR generators above, and the five old bot workflows were deleted.
• fix: Commons-only photos and logos, with credit fields in the API (ADR-018) TechEngine#124 (ADR-018): photos, logos and the images list must be Wikimedia Commons files. The API serves image_license/image_attribution for tablets, watches, PDAs, laptops and monitors. openapi.json declares the data license, CC BY-SA 4.0.

Also: pr-checks no longer skips the old bot branch names (refresh/, ingest/, verify/promote-, dump-refresh/). The README describes collect.yml and the verification in final-check.

Closes #297

Before the first run

Opening a PR with GITHUB_TOKEN needs Settings → Actions → General → "Allow GitHub Actions to create and approve pull requests". I'll turn it on when this merges. The default token stays read-only, and nothing here approves PRs.

Checks

• At 3c50cb8, the engine validator passes over all of develop.
• I ran python -m app.verify pr --base <sha> locally on the new engine. It exits 0 and prints the Tier 0-3 markdown.
• I ran the Report step's script locally on that output: tables and Mermaid colours survive, and @, #12, GH-7 and URLs are broken up.
• The three reusable workflows at 3c50cb8 are byte-identical to the version I reviewed in fix: honest crawler User-Agent; collection as manual PR generators TechEngine#127.
• pr-checks will run the full engine validator and a smoke dump, because the pin moves.

Checklist

• The PR targets develop (main only moves through release PRs)
• Sidebar filled in by hand. Projects needs the gh project scope, and Copilot is out of quota, so it was reviewed by hand.