feat(core): add honox framework target

[ysknsid25]

resolves: #175
Adds the hono/jsx reactivity adapter to @formisch/core and exposes it through the ./honox subpath.

---

_{Stack created with GitHub Stacks CLI • Give Feedback 💬}

Summary by CodeRabbit

• New Features
  • Added Honox as a supported framework option.
  • Added a reactive runtime with signals, batched updates, dependency tracking, and untracked execution.
  • Added unique identifier generation for reactive elements.
  • Exposed the Honox package export for application use.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: e666b836-b118-4493-ab76-7a0cd9945290

📥 Commits

Reviewing files that changed from the base of the PR and between 865212e and 1ee4be6.

📒 Files selected for processing (4)

• packages/core/package.json
• packages/core/src/framework/index.honox.ts
• packages/core/src/framework/index.ts
• packages/core/tsdown.config.ts

---

Walkthrough

Added Honox as a supported framework. Added a reactive runtime with signals, listener tracking, batched updates, and untracked callbacks. Registered Honox in the build configuration and exposed its generated JavaScript and type declaration files through the package exports.

Suggested reviewers: fabian-hiller

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Linked Issues check	⚠️ Warning	The adapter meets the Honox implementation objectives, but the change modifies existing files despite issue #175 requiring an additive change without such modifications.	Clarify or update issue #175 to permit the required package, framework type, and build configuration changes.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly identifies the addition of the Honox framework target.
Out of Scope Changes check	✅ Passed	The existing-file changes support the Honox adapter, package export, framework type, and build configuration described in the objectives.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

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.}

[Copilot]

Pull request overview

Adds a new Honox framework target to @formisch/core by introducing a Honox-specific reactivity adapter and wiring it into the build + package exports so consumers can import it via @formisch/core/honox.

Changes:

• Added a Honox framework adapter (index.honox.ts) implementing createSignal, batch, and untrack consistent with existing DOM-style adapters (notably React).
• Updated framework type unions to include 'honox' so the adapter can be selected/typed consistently.
• Updated build configuration and package exports to produce and expose dist/index.honox.* via the ./honox subpath.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File	Description
packages/core/tsdown.config.ts	Adds honox to the framework build matrix so index.honox artifacts are generated.
packages/core/src/framework/index.ts	Extends the Framework union type to include 'honox'.
packages/core/src/framework/index.honox.ts	New Honox adapter implementing core reactive primitives for this framework target.
packages/core/package.json	Exposes @formisch/core/honox via exports pointing to the new build outputs.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[cubic-dev-ai]

All reported issues were addressed across 4 files

<sub>Reply with feedback, questions, or to request a fix.

Re-trigger cubic</sub>

[fabian-hiller]

Thank you for working on this. I plan to review and merge it after our v1 release.