Fix repo.json: embed the manifest, don't just list its fields

Read the Homebrew Channel's own DetailsPanel.js: when an app is opened
from Browse, refresh() only ever takes entry.manifest directly, or
fetches entry.manifestUrl if that's absent — never the entry's own
top-level fields. Our repo.json had neither, so
resolveURL(undefined, repositoryURL) threw before the fetch could even
start, and the details screen spun on "Loading" forever with no visible
error. This is what happened when it was tried against a real repo.

Fixed by nesting the full manifest under a "manifest" key per package
entry, alongside the id/title/iconUri the Browse grid reads directly.
Verified structurally (grid fields present, manifest embedded and
non-empty, ipkUrl absolute) since there's no local Homebrew Channel
build to run this against.

Also caught in the same investigation: a stale --base-url in the docs
used the tag v1.0.0 while the actual release was tagged 1.0.0, which
404s the icon and ipk silently — same symptom, different cause. Noted
in both the tool's docstring and the docs that a tag mismatch looks
identical to the manifest bug from the client's side.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

docs/development.md

@@ -113,29 +113,37 @@ or ssh — the app installs itself once the TV can reach a URL.
 ### Your own repository (no review, no waiting)
 
 The Homebrew Channel's *Settings → Repositories → Add repository* accepts any
-URL that returns `{"packages": [...]}`, where each entry is the same manifest
-[`make-manifest.py`](../tools/make-manifest.py) already writes. Point one at
-your own git host's release assets and the app shows up in Browse with no
-submission process at all — this is what `--repo-out` (on by default) is for.
+URL that returns `{"packages": [...]}`. Each entry needs its own `id`/
+`title`/`iconUri` for the Browse grid, plus the full manifest nested under a
+`manifest` key for the details screen — [`make-manifest.py`](../tools/make-manifest.py)
+builds exactly that shape. Point one at your own git host's release assets and
+the app shows up in Browse with no submission process at all — this is what
+`--repo-out` (on by default) is for.
 
 1. Bump `version` in `frontend/appinfo.json`, `servicefiles/package.json` and
    `package.json`.
 2. Build the ipk: `./tools/docker-build.sh && ./tools/build.sh package` (or
    `./tools/build.sh` on Linux with the NDK installed).
-3. Create a release tagged e.g. `v1.0.0` and attach three files to it: the
-   ipk, `frontend/assets/icon.png`, and a repo index generated with
-   `--base-url` set to that release's asset URL:
+3. Create a release — note the **exact tag** Gitea/GitHub gives it, `1.0.0` or
+   `v1.0.0`, whichever it actually is — and attach three files: the ipk,
+   `frontend/assets/icon.png`, and a repo index generated with `--base-url`
+   set to that release's real download URL:
 
    ```sh
    python3 tools/make-manifest.py \
-     --base-url https://git.crylia.de/Crylia/lgtv_audio_cap/releases/download/v1.0.0
-   # -> out/manifest.json (one app entry)
-   # -> out/repo.json     (that entry wrapped as {"packages": [...]})
+     --base-url https://git.crylia.de/Crylia/lgtv_audio_cap/releases/download/1.0.0
+   # -> out/manifest.json (one app entry, for the official-repo route below)
+   # -> out/repo.json     ({"packages": [{id, title, iconUri, manifest: {...}}]})
    ```
 
+   A mismatched tag in `--base-url` doesn't error — it just makes the icon and
+   ipk links inside `repo.json` 404 silently, which looks identical to "the
+   details screen hangs" from the client's point of view. If the app was
+   already added and only the tag was wrong, re-run with the fixed tag and
+   re-upload `repo.json`; no need to touch the "Add repository" entry itself,
+   since its URL didn't change.
    Attach `out/repo.json` itself too — its own download URL is what you paste
-   into the TV, and it must match `--base-url` exactly or the ipk/icon links
-   inside it point at the wrong place.
+   into the TV.
 4. On the TV: Homebrew Channel → gear icon → *Add repository* → paste the
    `repo.json` release URL → back out to Browse → find *Audio Cap* → Install.