feat: operational tooling — signing, versioning, changelog, roadmap (SPEC-001)

Establish GuruConnect's release engineering and project tracking (SPEC-001):
- docs/ scaffold: FEATURE_ROADMAP, ARCHITECTURE_DECISIONS (ADR-001 standalone+contract,
  ADR-002 Gitea Actions + Azure Trusted Signing), docs/specs/SPEC-001, CHANGELOG.
- .gitea/workflows/release.yml: conventional-commit auto-versioning, git-cliff changelog,
  Windows agent build, Azure Trusted Signing via jsign (reusing the shared ACG cert profile),
  Gitea release via REST API. build-and-test.yml is the PR/push gate; deploy.yml de-duplicated.
- server: GET /api/changelog/:component/:version (latest + by-version), path-traversal hardened.
- cliff.toml; server/.env.example documents CHANGELOG_DIR.

Reviewed (Code Review Agent): axum route-conflict blocker fixed; CHANGELOG ordering, toolchain
target, breaking-change parsing, empty-changelog fallback addressed.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

server/.env.example

@@ -22,6 +22,12 @@ LISTEN_ADDR=0.0.0.0:3002
 # If set, persistent agents must provide this key to connect
 AGENT_API_KEY=
 
+# Optional: directory containing generated changelog files served at /api/changelog/...
+# Must point at the deployed `changelogs/` directory produced by the release workflow
+# (containing `LATEST_<COMPONENT>.md` and `<component>/v<version>.md`).
+# Defaults to ./changelogs, resolved relative to the server's working directory (CWD) when unset.
+CHANGELOG_DIR=./changelogs
+
 # Debug mode (enables verbose logging)
 DEBUG=false