Austin Schaefer eef98906b6 Add a Forgejo release source ... Packages can now declare source = "forgejo-release" plus a base_url and be checked, fetched and verified against a Forgejo instance's releases API, alongside the existing GitHub source. This is what lets pkgwatch track its own releases from the self-hosted Forgejo. - config: Source enum (github-release default, forgejo-release) + base_url, validated once at load (base_url pairing, http(s) scheme, and no github-attestation on a Forgejo source). - source: new module mapping a package to its Endpoints. - checker: latest_forgejo_release, one call to releases/latest; latest_release dispatches per source. - fetcher/verifier: take the releases API root instead of GithubEndpoints, since GitHub and Forgejo serve the same releases/tags/<tag> shape. - pipeline: endpoints are resolved per package. - docs: SPEC documents the source key and why the HTTP is hand-rolled rather than an API-client crate. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>		2026-09-20 10:36:13 +02:00
..
ARCHITECTURE.md	Move high-level docs into docs/, matching doubleo7's convention	2026-09-17 13:22:40 +02:00
SPEC.md	Add a Forgejo release source	2026-09-20 10:36:13 +02:00