|
| 1 | +# PR 11.84 — Asteroids Manifest Chrome Assets |
| 2 | + |
| 3 | +## Purpose |
| 4 | +Update the Asteroids `game.manifest.json` file so Workspace/Game launch uses declared manifest assets instead of guessed chrome asset paths. |
| 5 | + |
| 6 | +## Required change |
| 7 | +Find the Asteroids manifest, expected path: |
| 8 | + |
| 9 | +```text |
| 10 | +games/Asteroids/game.manifest.json |
| 11 | +``` |
| 12 | + |
| 13 | +Update or add the manifest asset entries so they resolve to: |
| 14 | + |
| 15 | +```json |
| 16 | +"image.asteroids.bezel": { |
| 17 | + "path": "/games/Asteroids/assets/images/bezel1.png", |
| 18 | + "kind": "image", |
| 19 | + "source": "workspace-manager" |
| 20 | +}, |
| 21 | +"image.asteroids.background": { |
| 22 | + "path": "/games/Asteroids/assets/images/deluxe.png", |
| 23 | + "kind": "image", |
| 24 | + "source": "workspace-manager" |
| 25 | +} |
| 26 | +``` |
| 27 | + |
| 28 | +## Guardrails |
| 29 | +- Do not add guessed fallback paths. |
| 30 | +- Do not modify other games. |
| 31 | +- Do not create placeholder image files. |
| 32 | +- Do not change shared asset-loading behavior in this PR. |
| 33 | +- Preserve existing manifest structure and ordering as much as possible. |
| 34 | + |
| 35 | +## Validation |
| 36 | +Run targeted checks only: |
| 37 | + |
| 38 | +```powershell |
| 39 | +Test-Path .\games\Asteroids\assets\images\bezel1.png |
| 40 | +Test-Path .\games\Asteroids\assets\images\deluxe.png |
| 41 | +Select-String -Path .\games\Asteroids\game.manifest.json -Pattern "bezel1.png|deluxe.png" |
| 42 | +``` |
| 43 | + |
| 44 | +Then open Asteroids through Workspace Manager and verify no request is made for: |
| 45 | + |
| 46 | +```text |
| 47 | +/games/Asteroids/assets/images/bezel.png |
| 48 | +/games/Asteroids/assets/images/background.png |
| 49 | +``` |
| 50 | + |
| 51 | +## Acceptance |
| 52 | +- Asteroids manifest references `bezel1.png` for bezel. |
| 53 | +- Asteroids manifest references `deluxe.png` for background. |
| 54 | +- No hardcoded fallback asset paths are introduced. |
| 55 | +- Targeted validation report is written under `docs/dev/reports`. |
0 commit comments