Skip to content

Upgrading lemonade-router-builder with the current Lemonade router - #292

Closed
sdevinenamd wants to merge 1 commit into
mainfrom
lemonade_router_builder_upgrade
Closed

sdevinenamd wants to merge 1 commit into
mainfrom
lemonade_router_builder_upgrade

Conversation

@sdevinenamd

Copy link
Copy Markdown
Collaborator

Changes

  • scripts/route_policy.schema.json is a verbatim copy of Lemonade's route_policy.schema.json. validate.py takes its allowed keys, condition types, classifier types and value checks from it instead of hard-coded lists. A small set of checks the schema can't express stays hand-written: ECMAScript regex, cross-references, and empty reference_phrases entries.
  • min_total_chars / max_total_chars are documented in SKILL.md and reference.md, and there's a new eval (long-conversation-router).
  • Server-side check: step 8b now starts with POST /api/v1/routing/validate (v11.6.0+), which runs the target server's own parser on the policy without registering it.

Verification

  • The bundled schema is identical to Lemonade main and to v2026.43.3.
  • All 29 policies in Lemonade's conformance tests and its router examples pass. The old validator rejected conditions_total_char_bounds.
  • 40 policies the server rejects are still rejected.

@github-actions

Copy link
Copy Markdown
Contributor

Closed: this is a vendored copy

skills/lemonade-router-builder is a mirror of a product repo, not source. The nightly federate-skills run re-imports the folder wholesale, so a change merged here is deleted the next time the source repo moves. Please make it upstream instead:

Vendored copy Edit it here Land it on
skills/lemonade-router-builder lemonade-sdk/skills/skills/lemonade-router-builder main

Once it is on that branch there, this catalog picks it up on its own (nightly, or by dispatching
federate-skills). See CONTRIBUTING.md.

Maintainers: if the change has to land here (retiring a federated skill, forcing a re-import), add the federation-override label and reopen.

@github-actions github-actions Bot closed this Oct 28, 2026
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