feat(spp): DOMA-12957 new spp user event model

[dkoviazin]

Added new model SppUserEvent for monitoring and analytics

Summary by CodeRabbit

• Chores
  • Updated registry-importer subproject reference to a newer commit; this is an internal update with no functional or behavioral changes to the application.
  • Minor manifest/meta update included; no action required from end users and review effort is minimal.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 32590321-1a0b-4c98-85de-24bbdc6d1d4b

📥 Commits

Reviewing files that changed from the base of the PR and between a0bab77 and 0e348c5.

📒 Files selected for processing (1)

• apps/registry-importer

🚧 Files skipped from review as they are similar to previous changes (1)

• apps/registry-importer

---

📝 Walkthrough

Walkthrough

A subproject commit reference in apps/registry-importer was updated from b8912d7bfde1cbbec9314db5746e0855daccf020 to 28bc80007e651bf7fe065ec9e10a89ed75401be6. No functional changes or source code modifications were introduced.

Changes

Cohort / File(s)	Summary
Subproject Reference Update apps/registry-importer	Commit reference bumped from b8912d7bfde1cbbec9314db5746e0855daccf020 to 28bc80007e651bf7fe065ec9e10a89ed75401be6; net +1/-1 lines, no functional changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 I hopped a commit, light as a feather,
A tiny SHA changed in springlike weather,
No code was harmed, no logic rearranged,
Just a pointer moved — delight unchanged,
I twitch my whiskers and thump for cheer.

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The PR title mentions 'new spp user event model' which aligns with the PR description stating 'Added new model SppUserEvent for monitoring and analytics', but the actual changes shown are only a subproject commit pointer update with no functional changes visible in the provided summary.	Clarify whether the title accurately represents the changes; if only a subproject pointer was updated, consider updating the title to reflect that (e.g., 'chore(spp): Update registry-importer submodule') rather than implying a new model implementation.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat/spp/Doma-12957/new_model_spp_user_event_for_etl

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[greptile-apps]

Confidence Score: 4/5

• The PR consists of infrastructure/configuration updates and submodule version bumps with no identified functional regressions, though commit message format should be corrected.
• This PR is safe to merge — the changes are primarily infrastructure, configuration, and submodule pointer updates. No critical logic or security issues were found. However, the scope is broader than initially described (multiple submodule updates plus significant workflow/config changes), and one commit has a minor message format violation (missing hyphen in task ID). The actual SppUserEvent model code in the submodule cannot be audited from this repository's diff. A score of 4/5 reflects confidence in the main repo changes while acknowledging that submodule internals should be reviewed in their own repositories.
• No files in the main repository require special attention. External submodule changes (registry-importer, eps, insurance, pos-integration, resident-app) should be reviewed in their respective repositories.

_{Last reviewed commit: 0e348c5}

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud