flowstate-dojo-community-epicdm-gateway-routes

Use this skill when a task touches packages/gateway-routes, imports @epicdm/gateway-routes, or needs to teach humans/agents how this package works.

Package identity:

• Package: @epicdm/gateway-routes
• Repository: epic-flowstate-community
• Version authority: package.json (0.1.7)
• Dojo course: flowstate-dojo-community-epicdm-gateway-routes

How to use the package:

• Purpose: Canonical gateway route table, logical service bindings, and environment emitters for FlowState
• Start with package-local docs when present.
• Verify details against source and tests before changing behavior.
• Use the Dojo course lessons as the teaching path: setup, mental model, core workflow, integration, feature labs, maintenance.

Public surfaces discovered:

• CfEmitOptions
• emitCfRoutes
• AgentService
• AgentPlugin
• KongEmitOptions
• JWT_CLAIMS_LUA
• emitKong
• LogicalService
• LocalUpstream
• CLOUD_BINDINGS
• LOCAL_BINDINGS
• UPSTREAM_TO_LOGICAL
• ROUTES
• SMOKE_SPECS
• RouteScope
• GatewayRoute
• SmokeExpect
• SmokeAuthMode
• SmokeSpec

Composable feature skilllets:

• CLOUD_BINDINGS: use feature labs for workflow, source anchor, and regression risk.
• Emit Cf Routes: use feature labs for workflow, source anchor, and regression risk.
• Emit Kong: use feature labs for workflow, source anchor, and regression risk.
• JWT_CLAIMS_LUA: use feature labs for workflow, source anchor, and regression risk.
• LOCAL_BINDINGS: use feature labs for workflow, source anchor, and regression risk.
• ROUTES: use feature labs for workflow, source anchor, and regression risk.
• SMOKE_SPECS: use feature labs for workflow, source anchor, and regression risk.
• UPSTREAM_TO_LOGICAL: use feature labs for workflow, source anchor, and regression risk.

Agent operating rules:

• Treat package.json as the Dojo version authority.
• Do not turn feature inventory into user-facing lessons without workflow context.
• Update this Dojo package when package behavior, docs, examples, or feature inventory changes.
• Verify downstream packages when package use and connection metadata shows inbound dependencies or references.
• Never mark publish status passed without successful cloud publish and catalog lookup.

Use this Dojo skill with package human docs, package-local feature inventory, agent-skillset.md, and the generated course.json in this folder. Keep this manifest version aligned with package.json.