Skip to content

Add runnable example exercise and end-to-end verification harness - #10

Open
kawasima wants to merge 2 commits into
developfrom
feature/examples-verification
Open

Add runnable example exercise and end-to-end verification harness#10
kawasima wants to merge 2 commits into
developfrom
feature/examples-verification

Conversation

@kawasima

Copy link
Copy Markdown
Member

Adds a self-contained example that doubles as a reference handout and an end-to-end verification harness, and rewrites the README with the platform concept.

What's here

  • examples/fizzbuzz/ — a standalone Maven exercise (stub, grading tests, self-scoring runner via kysymys-scorer-java, .mvn/extensions.xml, properties template, reference solution). Its README.md is the problem statement.
  • examples/bin/mint-jwt — HS256 dev-JWT helper matching BouncrBackend's claims (sub / permissions / …). Also makes the existing src/test/hurl/*.hurl scenarios runnable.
  • examples/verify.sh — drives the real loop against a dev server (auto-starts mvn exec:java if none is up).
  • README rewrite + a pointer to examples/.

What verify.sh proves (16/16)

Problem registration → real mvn kysymys:submit (sends git remote URL + commit) → answer recorded → review comment → local scoring = 100 → follow-offer notification → stuck/resolved telemetry → build events on the instructor /activity/status dashboard.

Finding: README vs. implementation gap

Posting a comment emits no event, so it generates no notification — there is no CommentPostedEvent, and RecordWhatsNew only reacts to SubmittedAnswerEvent / OfferedToFollowEvent. The README says "comments reach the learner as a notification", which is not yet wired. verify.sh reports this as a known gap and verifies the notification mechanism itself via the follow-offer path. examples/README.md documents this along with the other scope boundaries (no server-side scoring, dev HMAC token instead of the real Bouncr stack, best-effort Go watcher).

Scope note

Requires the kysymys SNAPSHOT modules in ~/.m2 (mvn -N install + install of kysymys-scorer-java / kysymys-maven-plugin / kysymys-activity-agent); the example project is standalone (not a reactor module).

🤖 Generated with Claude Code

kawasima and others added 2 commits July 17, 2026 12:09
A self-contained example that doubles as a reference handout and a verification
harness for the whole learning loop:

- examples/fizzbuzz/ — a standalone Maven exercise project (stub, grading tests,
  self-scoring runner via kysymys-scorer-java, .mvn/extensions.xml, properties
  template, reference solution).
- examples/bin/mint-jwt — HS256 dev-JWT helper matching BouncrBackend's claims.
- examples/verify.sh — drives the real loop against a dev server: register a
  problem, `mvn kysymys:submit`, review comment, notification, local scoring,
  stuck/resolved telemetry, and the instructor `/activity/status` dashboard.

verify.sh passes 16/16 and surfaces one README/implementation gap: posting a
comment emits no event, so it produces no notification (there is no
CommentPostedEvent); RecordWhatsNew only reacts to SubmittedAnswer /
OfferedToFollow. The script reports this as a known gap and verifies the
notification mechanism itself via the follow-offer path.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Replace the one-line stub with a concept-first README (problem it solves,
the learning loop, live work-activity telemetry, bounded contexts, modules,
getting started) and link to examples/ for the runnable exercise and the
end-to-end verification script.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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