ci: add Hatch. CI workflow

[sorted-ai-bot]

Summary

PmoQa CI導入指示書 (HATCH_CI_SETUP_INSTRUCTION.md) に基づき、Hatch. 固有の CI ワークフロー (.github/workflows/hatch-ci.yml) を新規追加します。

Scope

• hatch-safety (341 tests) と hatch-tui (108 tests) を PR / push 毎に自動実行
• 2 job 並列構成 (hatch-safety / hatch-tui)
• ubuntu-latest runner 使用（upstream の blacksmith runner 回避）
• concurrency グループで同一 PR の stale run を自動キャンセル
• permissions: contents: read で最小権限

Design Rationale

方針	理由
upstream の `test.yml` は触らない	fork merge 時の衝突防止 (V3P2-5)
Hatch. 固有の `hatch-ci.yml` を新規作成	Hatch. テストの成否を独立して可視化
`ubuntu-latest`	upstream の `blacksmith` runner は sorted-ai org で利用不可の可能性
2 job 構成	並列実行 + 個別の成否確認

Changes

• New: `.github/workflows/hatch-ci.yml` (57 lines)

Managed By

PmoQa Department. 本ワークフローは PmoQa 承認なしに変更してはなりません。

Test Plan

マージ後、初回 CI 実行で以下を検証:

1. `hatch-safety` job が PASS
2. `hatch-tui` job が PASS
3. 2 job が並列実行される
4. `concurrency` が機能する（同一 PR で 2 回 push して旧 run キャンセル確認）
5. Branch Protection 設定後、status check 未通過 PR が merge 不可になる

Reference

• Brief: `~/PmoQa/briefs/HATCH_CI_SETUP_INSTRUCTION.md`
• Priority: HIGH
• CEO 承認: 2026-04-06 取得済み

[github-actions]

This PR doesn't fully meet our contributing guidelines and PR template.

What needs to be fixed:

• PR description is missing required template sections. Please use the PR template.

Please edit this PR description to address the above within 2 hours, or it will be automatically closed.

If you believe this was flagged incorrectly, please let a maintainer know.

[github-actions]

Hey! Your PR title ci: add Hatch. CI workflow doesn't follow conventional commit format.

Please update it to start with one of:

• feat: or feat(scope): new feature
• fix: or fix(scope): bug fix
• docs: or docs(scope): documentation changes
• chore: or chore(scope): maintenance tasks
• refactor: or refactor(scope): code refactoring
• test: or test(scope): adding or updating tests

Where scope is the package name (e.g., app, desktop, opencode).

See CONTRIBUTING.md for details.

[sorted-ai-bot]

CI Failure Root Cause — Prerequisite Missing on origin/dev

CI failure is caused by a missing prerequisite on origin/dev, not by the workflow itself.

Verified facts

• origin/dev:packages/hatch-safety contains only package.json, src/index.ts, tsconfig.json
• origin/dev:packages/hatch-tui contains only package.json, src/index.ts, tsconfig.json
• No test files exist on origin/dev for either package
• The expected Hatch. test assets (341 + 108 = 449 tests) currently exist only on local dev

Evidence

=== origin/dev hatch-safety ===
packages/hatch-safety/package.json
packages/hatch-safety/src/index.ts
packages/hatch-safety/tsconfig.json

=== origin/dev hatch-tui ===
packages/hatch-tui/package.json
packages/hatch-tui/src/index.ts
packages/hatch-tui/tsconfig.json

=== local dev (not yet published) ===
packages/hatch-safety  : 50 files total, 20 test files
packages/hatch-tui     : 28 files total, 10 test files

CI Error

bun test v1.3.11
No tests found!
Tests need ".test", "_test_", ".spec" or "_spec_" in the filename
##[error]Process completed with exit code 1.

Conclusion

This PR is blocked by the unpublished Level 2 delta (dev ahead of origin/dev by 258 commits). The CI workflow itself is correct per PmoQa instruction (HATCH_CI_SETUP_INSTRUCTION.md), but cannot execute meaningful tests until the missing Hatch. package contents are published upstream.

This PR is moved to Draft until the missing Hatch. package contents are published to origin/dev.

Next Steps (not in this PR's scope)

1. Resolve Level 2: publish the 258 unpublished commits from local dev to origin/dev
2. Rerun CI on this PR to verify hatch-safety (341 tests) and hatch-tui (108 tests) pass
3. Mark PR ready for review and merge

References

• Brief: ~/PmoQa/briefs/HATCH_CI_SETUP_INSTRUCTION.md (PmoQa → Hatch. CTO)
• Follow-up Brief: ~/PmoQa/briefs/HATCH_LEVEL2_PUBLISH_GAP.md (Hatch. CTO → PmoQa, forthcoming)

---

Reported by: Hatch. CTO | 2026-04-06