[temmytopeabdulghaneey]

Closes #121. Adds Stryker configuration and a mutation-test script for correctness-critical modules.

[drips-wave]

@temmytopeabdulghaneey Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

[afeezorobsco-cyber]

@temmytopeabdulghaneey CI is failing on this branch against the latest main, so it can't be merged yet. The errors from the latest run:

Backend (typecheck + test + build)

npm ci
npm error Cannot read properties of null (reading 'edgesOut')

npm ci crashes (Cannot read properties of null (reading 'edgesOut')), which means backend/package-lock.json is malformed, usually from a hand-merged lockfile. Take main's lockfile (git checkout origin/main -- backend/package-lock.json), run npm install in backend/, and commit the result.

[github-actions]

@temmytopeabdulghaneey This PR now has merge conflicts with main, most likely because #190 (test(integration): end-to-end care-thread integration test scaffold) was just merged, so it can't be merged until it's rebased:

git fetch upstream            # upstream = https://github.com/DocForum/docforum-core.git
git rebase upstream/main
# resolve the conflicts, re-run the tests, then:
git push --force-with-lease

The usual culprits are shared docs like ROADMAP.md and ARCHITECTURE*.md. If the conflict is in the ROADMAP.md changelog, move your entry into a new file under changelog.d/ (see changelog.d/README.md) rather than resolving it in place, so it can't conflict again. CI re-runs when you push, and the needs-rebase label is removed automatically once the conflicts are resolved.

_{Automated message. It won't repeat unless the PR conflicts again after your next push.}

[github-actions]

✅ Malware scan: clean

The earlier findings are resolved as of 816f4f6.

[afeezorobsco-cyber]

Sweep: malware scan clean, CI green.

[github-actions]

@temmytopeabdulghaneey This PR now has merge conflicts with main, most likely because #222 (feat: add opt-in OpenTelemetry bootstrap) was just merged, so it can't be merged until it's rebased:

git fetch upstream            # upstream = https://github.com/DocForum/docforum-core.git
git rebase upstream/main
# resolve the conflicts, re-run the tests, then:
git push --force-with-lease

The usual culprits are shared docs like ROADMAP.md and ARCHITECTURE*.md. If the conflict is in the ROADMAP.md changelog, move your entry into a new file under changelog.d/ (see changelog.d/README.md) rather than resolving it in place, so it can't conflict again. CI re-runs when you push, and the needs-rebase label is removed automatically once the conflicts are resolved.

_{Automated message. It won't repeat unless the PR conflicts again after your next push.}

[zeemscript]

Hi @afeezorobsco-cyber — I rebased PR #218 and regenerated backend/package-lock.json against the current manifest. npm ci --ignore-scripts --no-audit --no-fund passes locally, and GitHub reports no conflicts. The malware scan passes; CI is awaiting maintainer approval (action_required). Please approve/run CI when available.

[afeezorobsco-cyber]

Sweep: malware scan clean, CI green.