[joshschmelzle]

Why

REPOS.md had become a working list. Changelog versions, tag gaps, Dependabot failures, and per-repo action items go stale every time a release ships. The WLAN Pi Engineering Lead digest tracks that live status.

What changed

REPOS.md is now a stable map. Each active repo has a name and link, a one-line purpose, the default branch, the package name, how it builds and releases, and whether deploy-to-packagecloud.yml calls tag-release. Promotion from Packagecloud wlanpi/dev to wlanpi/main is stated once, as a manual step. wlanpi-bridge, wlanpi-server, and wlanpi-wconsole stay in Retired, and all three are archived. wlanpi-chat-bot is listed there too, because it is archived.

Links that pointed at the removed sections (#ci, #packaging, #release-tags, and "Deviations from target") now point at the map, or the pointer is gone. The removed lists were not copied into another file.

Before

• Applications table: branch, packaging tool, Python, lint, license, README shape.
• Platform and tooling tables, plus a Retired note.
• Deviations: debian/compat, source format, changelog versions, Standards-Version, CI gaps, Dependabot, a release-tag table, and license migration items.

After

• Intro: this file is a stable map. Current versions are in debian/changelog and on GitHub Releases.
• Applications, platform, and tooling tables: purpose, default branch, package, build and release, tag-release.
• Packagecloud promotion: manual, after testing. wlanpi-desktop promote-to-main.yml is workflow_dispatch.
• Retired: wlanpi-bridge, wlanpi-server, wlanpi-wconsole, and wlanpi-chat-bot are archived.

Scope

• Started from main after docs: bring the repository snapshot up to date #46 merged. No trim commit was pushed to the merged branch.
• wlanpi-app is not in the map. GET /repos/WLAN-Pi/wlanpi-app returned 404, so this change does not repeat the old row.
• Does not add org repos that were already outside the map.

Verification

Each row was read from the GitHub API on the default branch: repo description, archived, debian/control Source and Package, and uses: lines in the build and deploy workflows.

deploy-to-packagecloud.yml calls tag-release on wlanpi-bluetooth, wlanpi-core, wlanpi-fpms, wlanpi-librespeed-cli, and wlanpi-mcp. The previous snapshot did not include wlanpi-fpms.

Evidence

Archived: wlanpi-bridge, wlanpi-server, wlanpi-wconsole, wlanpi-chat-bot. Removal from trixie images: wlanpi-common#111, pi-gen#108.

tag-release callers: wlanpi-bluetooth deploy, wlanpi-core deploy, wlanpi-fpms deploy, wlanpi-librespeed-cli deploy, wlanpi-mcp deploy.

Promotion: sbuild-deploy-pkg.yml pushes to wlanpi/dev. promote-to-main.yml runs on workflow_dispatch and pushes to wlanpi/main.

Kernel package file names come from build-and-archive-kernel-package.yml. wlanpi-misc-packages package names come from each debians/<name>/control and from the matrix in build-packages.yml.

  

---

Note

Low Risk
Documentation-only reshaping of REPOS.md and link text; no runtime, CI, or packaging behavior changes in application repos.

^{Reviewed by Cursor Bugbot for commit f6a2617. Bugbot is set up for automated code reviews on this repo. Configure here.}