growqr-app/growqr-backend
3
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity

Canonical service registry events and onboarding ledger merge #14

Closed
Sai-karthik wants to merge 0 commits from karthiksaiketha/prm-80-backend-canonical-service-event-contract-for-streaks-qscore into staging
pull from: karthiksaiketha/prm-80-backend-canonical-service-event-contract-for-streaks-qscore
merge into: growqr-app:staging
Conversation 0 Commits - Files Changed -
Sai-karthik commented 2026-06-28 08:30:47 +00:00
Owner
Copy Link

Summary

  • Merges PR #13 (backend-canonical-fix) into this backend branch so the onboarding ledger becomes the canonical onboarding completion source and triggers curator/QScore side effects.
  • Moves canonical service event contracts directly into each service entry in src/services/service-registry.ts; no separate canonical-service-events file and no exported standalone event-contract type.
  • Exposes the per-service eventContract through service catalog/capability surfaces so curator/workflow callers can read event metadata from the registry itself.
  • Aligns curator completion recognition with the new canonical service events and fixes the roleplay smoke health port to 8040.

What was merged from PR #13

  • Added canonical onboarding ledger helpers in src/events/onboarding-ledger.ts.
  • Added onboarding ledger smoke coverage in scripts/onboarding-ledger.test.ts.
  • Updated onboarding status and event routes to rely on valid onboarding ledger events.
  • Wired onboarding ledger ingestion through HTTP events, v1 event tracking, and Redis consumption.
  • Triggered QScore baseline seeding and curator onboarding plan generation from canonical ledger events.

Canonical service events now in registry

The registry now carries event contracts inline for:

  • interview-service: preview/session configured/completed/abandoned and feedback events.
  • roleplay-service: preview/scenario configured/completed/abandoned and feedback events.
  • resume-service: uploaded, parsed, analysis completed, updated, exported.
  • cover-letter-service: generated, edited, exported.
  • courses-service: generated, started, lesson completed, completed, weakness applied.
  • assessment-service: started and completed measurement events.
  • matchmaking-service: matches generated, feed viewed, match viewed/saved/dismissed, application started/completed.
  • qscore-service: baseline created, review opened, weak driver reviewed, signal projected, updated.
  • social-branding-service: brand post drafted/edited/exported, profile updated, content published.

Verification

  • npm run typecheck
  • npm run test:onboarding
  • Rebuilt and restarted growqr-backend; container is healthy.
  • curl http://localhost:4000/healthz returned {"ok":true}.
## Summary - Merges PR #13 (`backend-canonical-fix`) into this backend branch so the onboarding ledger becomes the canonical onboarding completion source and triggers curator/QScore side effects. - Moves canonical service event contracts directly into each service entry in `src/services/service-registry.ts`; no separate `canonical-service-events` file and no exported standalone event-contract type. - Exposes the per-service `eventContract` through service catalog/capability surfaces so curator/workflow callers can read event metadata from the registry itself. - Aligns curator completion recognition with the new canonical service events and fixes the roleplay smoke health port to `8040`. ## What was merged from PR #13 - Added canonical onboarding ledger helpers in `src/events/onboarding-ledger.ts`. - Added onboarding ledger smoke coverage in `scripts/onboarding-ledger.test.ts`. - Updated onboarding status and event routes to rely on valid onboarding ledger events. - Wired onboarding ledger ingestion through HTTP events, v1 event tracking, and Redis consumption. - Triggered QScore baseline seeding and curator onboarding plan generation from canonical ledger events. ## Canonical service events now in registry The registry now carries event contracts inline for: - `interview-service`: preview/session configured/completed/abandoned and feedback events. - `roleplay-service`: preview/scenario configured/completed/abandoned and feedback events. - `resume-service`: uploaded, parsed, analysis completed, updated, exported. - `cover-letter-service`: generated, edited, exported. - `courses-service`: generated, started, lesson completed, completed, weakness applied. - `assessment-service`: started and completed measurement events. - `matchmaking-service`: matches generated, feed viewed, match viewed/saved/dismissed, application started/completed. - `qscore-service`: baseline created, review opened, weak driver reviewed, signal projected, updated. - `social-branding-service`: brand post drafted/edited/exported, profile updated, content published. ## Verification - `npm run typecheck` - `npm run test:onboarding` - Rebuilt and restarted `growqr-backend`; container is healthy. - `curl http://localhost:4000/healthz` returned `{"ok":true}`.
Sai-karthik added 3 commits 2026-06-28 08:30:48 +00:00
feat: implement onboarding ledger event handling and related tests 685f2dcd24
Merge remote-tracking branch 'origin/pr/13' into karthiksaiketha/prm-80-backend-canonical-service-event-contract-for-streaks-qscore 52589fc76d
fix: inline service registry event contracts 1b90e5db39
Sai-karthik closed this pull request 2026-07-01 10:30:16 +00:00

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
dv OG puter Sai-karthik
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: growqr-app/growqr-backend#14
No description provided.
Delete Branch "karthiksaiketha/prm-80-backend-canonical-service-event-contract-for-streaks-qscore"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?