[#190] Make chapter title required on chain page

[realproject7]

Summary

• Chapter title field is now required (label updated, no longer "(optional)")
• Submit button disabled when title is empty
• Validation message "Title is required" shown when content is entered but title is blank

Test plan

• Cannot submit with empty title — button disabled
• Validation message appears when content typed but title empty
• Can submit normally with both title and content filled
• Title still capped at 100 characters

Fixes #190

🤖 Generated with Claude Code

[project7-interns]

T2b: APPROVE

Clean change: title made required with trim() validation, submit button disabled when empty, error message shown contextually (only when content has been entered). Character counter preserved.

[project7-interns]

Verdict: REQUEST CHANGES

Summary

The required-title behavior is correctly wired, but the PR still misses two explicit UI details from issue #190. Since this ticket is narrowly scoped to the field contract, those details should match the spec exactly.

Findings

• [medium] Chapter-title placeholder does not match the issue copy
  • File: src/app/chain/page.tsx:151
  • Suggestion: use the requested placeholder text e.g. The Silent Storm instead of e.g. The Awakening so the field matches the issue spec.
• [medium] Character counter format does not match the issue copy
  • File: src/app/chain/page.tsx:161
  • Suggestion: render the counter in the requested 42 / 100 chars style. The current output is ${title.length}/100, which omits the spaces and chars suffix called for in #190.

Decision

Requesting changes because #190 gives explicit field-copy acceptance criteria, and the current UI still diverges from those details.

[project7-interns]

Verdict: APPROVE

Summary

The follow-up change brings the remaining field copy into line with issue #190: the placeholder now uses the requested example text and the counter now renders in the specified 42 / 100 chars format. The required-title behavior remains intact, and the updated head passes GitHub lint-and-typecheck.

Findings

• None.

Decision

Approving because the previously flagged copy mismatches are resolved and the chain-page title field now matches the issue spec.