[JUM-917][Release] Sync main cli-init 0.0.1 bump into den

[web2solutions]

Summary

• Sync main → dev after #625 (@jumentix/cli-init 0.0.0→0.0.1) and changelog #624.

Problem Statement

Tips drifted after the automated bump/changelog landed on main post-#623.

• Related issue(s): https://linear.app/jumentix/issue/JUM-917
• Related PR(s): chore(release): bump packages with unpublished content changes #625
• Related check run(s): pending

Project Tracking (Required)

• Linear Project: Jumentix (https://linear.app/jumentix)
• Focused epic link: https://linear.app/jumentix/project/epicdocs-jumentix-website-deep-docs-playgrounds-seoai-dae8af894bf6
• Epic milestone: n/a
• Primary task nature: release
• Epic-delegated agent ID: cursor
• Child task issue link: https://linear.app/jumentix/issue/JUM-917
• Project Update: final tip sync after cli-init bump
• Linear Project link(s): https://linear.app/jumentix/project/epicdocs-jumentix-website-deep-docs-playgrounds-seoai-dae8af894bf6
• Linear Issue link(s): https://linear.app/jumentix/issue/JUM-917
• Linear Issue ID list (comma separated): JUM-917
• Item status at PR creation: Done; final sync
• Target cycle (Start date -> End date): 2026-10-06 -> 2026-10-06
• Priority group for this PR (P0 / P1 / P2): P1
• This PR contains tasks from only one priority group.

Branch Promotion Path (Required)

• Source branch: main
• Target branch: dev
• Required PR title format: [JUM-XXXX][Nature] <concise outcome>
• The leading JUM-XXXX matches the single Linear Issue declared above.
• This task PR targets dev.
• If this PR targets main, it is a release promotion sourced from dev, references the task PRs/issues already merged into dev, and introduces no unreviewed changes.
• This PR is not a direct task/topic branch promotion to main.

Bidirectional Traceability (Required)

• Every linked issue already contains this PR URL.
• Every linked issue already contains commit hash/range evidence.
• PR description includes mapping of task -> commit(s).
• Task -> commit(s) mapping:
  • JUM-917: sync of 7ea8d962 (chore(release): bump packages with unpublished content changes #625) + #624

Scope of Change

Domain / Business Rules

• None.

Application / Use Cases

• None.

Adapters / Infrastructure

• Sync only.

API / Contracts (OpenAPI, DTOs, handlers, controllers)

• None.

Detailed Technical Changes

1. Sync main tip into dev.

Architecture and Design Alignment

• Domain logic remains inside domain/application layers.
• Controllers/handlers do not instantiate repositories/services directly.
• Ports/adapters boundaries are respected.
• No new circular dependencies introduced.
• Event publishing/listening flow remains consistent.

Security Impact

• Security impact: No security impact
• Secrets handling reviewed: [x] N/A
• Input/output sanitization reviewed: [x] N/A
• AuthN/AuthZ impact: [x] No
• Data exposure risk (password/salt/token/PII): [x] No
• Sonar security findings addressed or unaffected: [x] Yes

Data and Migration Impact

• Data model impact: None
• Migration required: [x] No
• Rollback strategy: Revert sync on dev.

Breaking Changes

None

Acceptance Criteria

• Sync targets dev from main.
• CI green / mergeable.
• Tips aligned.

Test Plan (Evidence)

• Hosted CI — pending

Feedback Resolution (Required)

• Every GitHub review thread is resolved natively.
• Every general comment has a visible resolution response by the PR author or a repository maintainer.
• Each resolution response uses exactly one marker and, for resolved, a SHA from this PR:

<!-- jumentix-pr-feedback: resolved comment=https://github.com/OWNER/REPO/pull/NUMBER#issuecomment-ID commit=PR_COMMIT_SHA -->
<!-- jumentix-pr-feedback: invalid comment=https://github.com/OWNER/REPO/pull/NUMBER#issuecomment-ID -->

Coverage

• Project coverage >= 95%: [ ] Yes [ ] No (pending CI)
• Patch coverage >= 95%: [ ] Yes [ ] No (pending CI)
• Codecov status passing: [ ] Yes [ ] No (pending CI)

SonarQube Cloud

• Quality Gate passing: [ ] Yes [ ] No (pending CI)
• New vulnerabilities introduced: [x] No
• New security hotspots reviewed: [x] N/A

Performance / Reliability Impact

None

Documentation Impact

• N/A

Release / Ops Notes

Final tip alignment for JUM-917.

Risk Assessment

• Risk level: Low
• Blast radius: dev tip
• Rollback: Revert sync

Checklist

• Sync main → dev
• References JUM-917

Made with Cursor

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
jumentix-website	Ready	Preview	Oct 6, 2026 9:46pm UTC

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: e2268f87-6698-4728-a209-809746bc5baa)

[cursor]

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 54b0056d-98b4-4a51-9399-29fe790026d0)