catalogue: io.pilot.bowmark v1.0.0 - #448
Open
Alexgodoroja wants to merge 2 commits into
Open
Conversation
Bowmark pivoted: bowmark.ask and bowmark.report_outcome are retired upstream and the API 404s both, so every command on the current store page fails today. v1.0.0 replaces them with bowmark.get_library and bowmark.run. Four platform bundles are live on the prod artifact registry under io.pilot.bowmark/1.0.0/, all signed by the app's existing publisher key (ed25519:Lmf0vzz0...), unchanged since 0.1.0. The store page is regenerated from the v1.0.0 submission rather than carried over: description, tagline, methods and keywords all described the retired methods. Changelog notes are the publisher's own (a submission has nowhere to carry a changelog, so the generated placeholder would have read 'Released v1.0.0').
Replaces the generator's output with a hand-authored page. Every field is set explicitly; the prose blocks (description_md, product_demo, next_steps) are lifted verbatim from the merged submission, so the page cannot drift from what was reviewed. Two departures from the generated version: - methods lists the callable surface only: get_library, run and the help discovery contract, as 0.1.0 did. - changelog carries the publisher's own v1.0.0 notes above the 0.1.0 history, instead of the generated 'Released v1.0.0' placeholder. metadata_sha256 re-pinned to the committed bytes and catalogue.json re-signed; pilot-app verify is green on all ten checks for this entry.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Catalogue entry for io.pilot.bowmark v1.0.0, the update merged as app-template#97.
Bowmark pivoted.
bowmark.askandbowmark.report_outcomeare retired upstream andapi.bowmark.ai404s both, so every command on the current store page fails today — the broker access log has real callers hitting/v1/askand getting 404 as recently as this evening. v1.0.0 replaces them withbowmark.get_library(typed function library) andbowmark.run(server-side script execution on the live sites).Artifacts
All four platform bundles are live on the prod artifact registry under
bundles/io.pilot.bowmark/1.0.0/, each fetched back over its public URL and sha-checked:3b4800e811bb684f…d5fb05bb39cbe727…be84e356e53bbabd…325c554e66fbf0fb…Publisher pin is
ed25519:Lmf0vzz0CNPu94pbqsbD/ueSuOaKsGc0xU/DoL+Yu7c=— the same key that published 0.1.0, so the update gate's ownership check passes.pilot-app verify catalogue/catalogue.jsonis green on this entry across all ten checks.catalogue.jsonis re-signed and the signature verifies under the embedded trust anchor;metadata_sha256is the sha of the bytes committed here. Catalogue stays atversion: 2.Opened by hand, and why
publish-on-mergeran on the app-template merge, found all four bundles on R2 and verified the primary — then failed at the catalogue step.CATALOG_PUBLISH_TOKENis dead; the same failure killed firecrawl (#95) today and agentphone (#93) on 29 Jul, so nothing has auto-published for over a week. Worth rotating.Store page regenerated, not carried over
For an app that already has a
metadata.json,publish-rich-from-r2.shreuses it and refreshes onlypublisher,size,product_demoandnext_steps. On a pivot like this that ships a half-updated store page: the new demo and next-steps graph beside adescription_md,tagline,methodslist andkeywordsstill describing the retiredask/report_outcome. This page is hand-authored from the v1.0.0 submission instead — every field set explicitly, with the prose blocks (description_md,product_demo,next_steps) lifted verbatim from the merged submission so the page cannot drift from what was reviewed. The methods list is the callable surface:get_library,run, and thehelpdiscovery contract, as 0.1.0 had. Filing the reuse behaviour against the script separately.The changelog notes are the publisher's own, from the PR discussion.
SubListinghas nochangelogfield andToConfigdoes not map one, so a submission cannot carry one and the generated default would have read "Released v1.0.0".