Skip to content

submit: io.pilot.bowmark — add report_outcome endpoint + expand docs#63

Merged
Alexgodoroja merged 1 commit into
mainfrom
update/io.pilot.bowmark-report-outcome
Jul 3, 2026
Merged

submit: io.pilot.bowmark — add report_outcome endpoint + expand docs#63
Alexgodoroja merged 1 commit into
mainfrom
update/io.pilot.bowmark-report-outcome

Conversation

@Alexgodoroja

Copy link
Copy Markdown
Collaborator

Follow-up to #62. Covers the second Bowmark REST endpoint and enriches the listing.

  • Adds bowmark.report_outcome (POST /v1/outcomes) alongside bowmark.ask — after running a recipe, the agent reports whether it executed cleanly, which feeds Bowmark's re-crawl loop that keeps recipes healthy.
  • Expands bowmark.ask with the full response/status contract (ok / no_useful_data / site_not_supported / ambiguous_scope / rate_limited / 503), the variants facets (auth_state, role, locale, region, currency), scopeHint, and step flags (irreversible / requires_user_input).
  • Sets the listing license to Proprietary to match the hosted Bowmark service.

Both endpoints validated end-to-end on the pilot-publish broker (allow-list /v1/ask + /v1/outcomes) and via a local prod-R2 catalogue install.

Adds the second Bowmark REST endpoint bowmark.report_outcome (POST
/v1/outcomes) alongside bowmark.ask, documents the full ask syntax
(statuses, variants, scopeHint, step flags) and edge cases, and sets the
listing license to Proprietary to match the hosted service.
@Alexgodoroja Alexgodoroja merged commit f51087d into main Jul 3, 2026
7 checks passed
@Alexgodoroja Alexgodoroja deleted the update/io.pilot.bowmark-report-outcome branch July 3, 2026 23:52
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