Campaign lifecycle: FORMING → RUNNING ⇄ HIATUS → CONCLUDED
- 主要言語
- HTML
- スター
- 0
- フォーク
- 0
- 平均マージ
- 1時間 34分
- マージ済み PR(30日)
- 23
説明
`FORMING → RUNNING ⇄ HIATUS → CONCLUDED`.
- [ ] State column + transitions as one function; every transition writes `audit_log`.
- [ ] Signup buttons exist only in FORMING. Starting a campaign closes the roster; **a closed roster never reopens on its own.**
- [ ] Started campaigns skip stages 1 and 2 structurally — a campaign entered directly as RUNNING (the four existing ones) gets its roster from `campaign_members`, not from signups.
- [ ] HIATUS pauses materialisation; RUNNING resumes it from the anchor. CONCLUDED stops it for good.
- [ ] `max_sessions` reached → CONCLUDED, or prompt the GM (organiser's call).
コントリビューションガイド
このリポジトリのコントリビューションガイドは索引されていません
調査の方向性
Start by tracing the campaign state column, transition function, signup buttons, materialisation, audit_log, campaign_members, and max_sessions references. Done means all listed lifecycle transitions and roster rules work, audit_log records every transition, HIATUS and CONCLUDED control materialisation correctly, and directly RUNNING campaigns use campaign_members.
索引モデルが issue の本文から書いたものです。
評価
- 領域
- backend, database
- issue の種類
- 機能追加
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 活発さ
- 活発
- 明瞭さ
- おおむね明確
- 初心者へのやさしさ
- 35/100