davsclaus opened a new pull request, #75: URL: https://github.com/apache/camel-jbang-examples/pull/75
The first step of CAMEL-24808 (revamp into a real-world ladder). Metadata only, no route changes, in two commits. **Commit 1, the metadata pass over all 30 examples** - `level` becomes the group an example belongs to instead of a difficulty that mixed with infrastructure: `quick-start` (timer-log, rest-api, routes, splitter, kept generic), the ladder rungs `run`, `transform`, `route`, `fail-well`, `connect`, `connect-service`, `contracts`, `ai`, `cloud`, and `showcase` for the tooling demos (memory-leak, message-size, tui-hello-world, smart-log-analyzer). - Every `description` now states what you observe when the example runs: what triggers, what happens, what the log or the endpoint shows. A reader and a harness can tell pass from fail, and an assistant gets the behaviour as its task rather than a topic. - A new `teaches` field lists the components, EIPs, languages and data formats an example introduces, for the recipes catalog (CAMEL-23774) and for any assistant that picks examples. - `generate-catalog.sh` passes `teaches` through, the catalog is regenerated, and the metadata table in `AGENTS.md` describes the fields. **Commit 2, four examples dropped**: cron-log (timer-log with a cron expression; a nightly report on the ladder will show cron in a real setting), financial-doc-analyzer (a second Docling example), keycloak-introspection-rest (a variant of keycloak-security-rest), aws-s3-event-based (EventBridge, SQS and a real account). 26 remain. The Camel CLI lists examples grouped by the three old level names and tolerates other values, so the new groups show after them until the CLI listing is updated (step 4 of the Jira). The additions, rung by rung, and the "Build it step by step" README sections follow in later PRs. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01Bp3538HRBPMQkb5ta9xRaj -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
