Skip to content

app-store: Bowmark v1.0.0, pinned to New & Updated - #193

Open
Alexgodoroja wants to merge 1 commit into
mainfrom
app/bowmark-v1
Open

app-store: Bowmark v1.0.0, pinned to New & Updated#193
Alexgodoroja wants to merge 1 commit into
mainfrom
app/bowmark-v1

Conversation

@Alexgodoroja

@Alexgodoroja Alexgodoroja commented Aug 4, 2026

Copy link
Copy Markdown
Collaborator

Store card, app page and plain twin for Bowmark v1.0.0 — the update merged as app-template#97, catalogue entry in pilotprotocol#448.

Bowmark pivoted. bowmark.ask and bowmark.report_outcome are retired upstream and api.bowmark.ai 404s both, so every command on the current card and app page fails today. v1.0.0 replaces them with bowmark.get_library (a typed function library for the live web) and bowmark.run (a short JavaScript body executed server side on the real sites).

What changed

  • Pinned first in New & Updated, per request.
  • Tagline, description, keywords, version, sizes and changelog refreshed from the catalogue snapshot in pilotprotocol#448, so the page matches what actually installs.
  • Methods list rewritten: get_library + run.
  • Product demo carried through verbatim — 5 examples, and no longer marked metered (v0.1.0 advertised a cost block the app no longer has).
  • Changelog carries the publisher's own v1.0.0 notes above the 0.1.0 history. The retired method names still appear there, which is the point of a changelog.

Verification

  • apps.ts regenerated with scripts/gen-apps.mjs. Every changed line falls inside the Bowmark record — I diffed the generated file against a regeneration from main and confirmed zero churn to the other 21 apps.
  • npm run build green, check:site green (384 files, 24,967 internal references), check:plain green.
  • Rendered /apps/io.pilot.bowmark shows v1.0.0 with both new methods; the only ask/report_outcome occurrences left on the page are inside the changelog.

Plain twin

Re-stamped rather than regenerated. The only change to the human source is the order of the freshPinned array, and src/pages/plain/app-store.astro is 24 lines of static prose with no app list, no ids and no iteration — so shelf order cannot alter its rendered content. I checked that directly rather than assuming it.

Note on ordering

Branched from main, so this touches the same freshPinned line as #192 (Firecrawl). Whichever lands second needs a one-line rebase — happy to take that side.

Bowmark pivoted. bowmark.ask and bowmark.report_outcome are retired upstream
and api.bowmark.ai 404s both, so every command on the current store page fails
today. v1.0.0 replaces them with bowmark.get_library (typed function library)
and bowmark.run (server-side script execution on the live sites).

Data comes from the catalogue snapshot in pilot-protocol/pilotprotocol#448, so
the page matches what installs: tagline, description, keywords, version, sizes
and changelog, plus the rebuilt product demo carried through to the page and its
plain twin.

Pins io.pilot.bowmark first in the New & Updated shelf.

The methods list carries the two product methods. bowmark.help is boilerplate on
every app, and the generator's auto-added bowmark.balance answers only for apps
with a broker credit ledger — this one has none, so it 403s and is not worth
advertising.

apps.ts regenerated: every changed line falls inside the Bowmark record, no
churn to other apps. Plain twin re-stamped; it is static prose with no app list,
so shelf order cannot change its content (verified). check:plain, check:site and
the build are green.

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

github-actions Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

🚀 Preview deployed to Cloudflare Pages

  • Commit deploy URL: https://e9789b01.pilotprotocol.pages.dev
  • Branch alias: https://app/bowmark-v1.pilotprotocol.pages.dev (may take ~30s to propagate)
  • Commit: c60ead1011cfaf1d71990ac6c7a5c3c29c762eda

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant