Move manu-schwendener-DSwBHyWKiVw-unsplash.jpg to the front of the
Nature feed order so it is the default (first) photo — the same image
the welcome screen already shows. The Nature feed event must be
republished for it to take effect.
Add manu-schwendener-DSwBHyWKiVw-unsplash.jpg (the bundled welcome and
fallback image) as a photo in the Nature feed with its Unsplash
attribution, and append it to the feed order.
The original still needs to be uploaded to Blossom and the photo and feed
events republished before the app sees it (see scripts/nostr/README.md).
Releases were built and signed in CI, which meant AMO credentials had to
live on the runner. Move the whole flow local: builds and Firefox signing
happen on the maintainer's machine and only the finished artifacts are
published.
Add `ext:pack:firefox` and `ext:pack:chrome` (production builds; the
Firefox one is signed via `web-ext sign` unlisted with credentials read
from the GNOME Keyring through `secret-tool`, the Chrome one is zipped)
and wire them to the `version` lifecycle:
- `preversion` runs lint and tests.
- `version` builds and signs into `web-ext-artifacts/`.
- `postversion` pushes the bump commit and tag, then uploads both
artifacts to the Gitea release and publishes it if still a draft.
Switch the plain `ext:build:*` scripts to production and add
`ext:build:dev:*` for development builds; `ext:dev` is unchanged. The
build manifest now takes its version from package.json and drops the
"(dev)" name suffix when `DASHTAB_RELEASE=1`.
Because packaging needs a production build, relax the AGENTS.md
production-build restriction to allow it for packaging and releasing.
Read the curated photo feeds from wss://nostr.kosmos.org, verify events, cache originals and thumbnails, and let users pick a wallpaper from the Photos section. Nature is the default feed; City Nights is opt-in. Adds the manual publishing scripts, real event fixtures, protocol documentation, and tests with stubbed network connections.