Skip to content

feat(machines): remove owner notes field (PP-blue)#1585

Open
timothyfroehlich wants to merge 1 commit into
mainfrom
feat/remove-owner-notes-PP-blue
Open

feat(machines): remove owner notes field (PP-blue)#1585
timothyfroehlich wants to merge 1 commit into
mainfrom
feat/remove-owner-notes-PP-blue

Conversation

@timothyfroehlich

Copy link
Copy Markdown
Owner

Removes the per-machine private Owner Notes prose field. It's unused and not very discoverable.

Prod audit (2026-06-25): of 115 machines, 0 had owner_notes set, and there were 0 owner_notes_updated timeline events — no real data or activity history is lost. Mirrors the tournament-notes removal (#1554).

Owner requirements is intentionally kept — only owner notes is removed.

Changes

  • schema: drop machines.owner_notes column (migration 0046_goofy_shape.sql)
  • actions: delete updateMachineOwnerNotes; drop ownerNotes from the prose-field unions + PROSE_FIELD_TO_EVENT_KIND; simplify the per-field permission special-casing (only machines.edit remains)
  • permissions: remove machines.edit.ownerNotes + machines.view.ownerNotes matrix entries (help page auto-generates from the matrix)
  • timeline: drop owner_notes_updated event kind, formatter case, icon
  • ui: remove the field + canView/canEditOwnerNotes props from the machine info tab and page.tsx; update owner-assignment copy
  • seed: drop the owner_notes_updated demo event; switch the demo idempotency sentinel to owner_requirements_updated
  • e2e: drop owner_notes from clearMachineField union
  • tests: drop ownerNotes assertions across unit + integration suites

Verification

  • pnpm run check ✅ (1306 unit/integration tests, typecheck:tests baseline gate clean)
  • pnpm run preflight ✅ Pre-flight checks passed (types, lint, build, PGlite integration 355 + 104)
  • pnpm db:generate reports no schema drift; local DB confirms owner_notes dropped, owner_requirements retained

Closes PP-blue.

🤖 Generated with Claude Code

The per-machine private "Owner Notes" prose field is unused and not very
discoverable, so remove it. Prod audit before removal (2026-06-25): of 115
machines exactly 0 had `owner_notes` set, and there were 0
`owner_notes_updated` timeline events — no real data or activity history is
lost. Mirrors the tournament-notes removal (#1554). Owner *requirements* is
intentionally kept.

- schema: drop machines.owner_notes column (migration 0046)
- actions: delete updateMachineOwnerNotes; drop ownerNotes from the prose-field
  unions + PROSE_FIELD_TO_EVENT_KIND; simplify the per-field permission
  special-casing (only machines.edit remains)
- permissions: remove machines.edit.ownerNotes + machines.view.ownerNotes
  matrix entries (help page auto-generates from the matrix)
- timeline: drop owner_notes_updated event kind, formatter case, icon
- ui: remove the field + canView/canEdit OwnerNotes props from the machine
  info tab and page.tsx; update owner-assignment copy
- seed: drop owner_notes_updated demo event; switch the demo idempotency
  sentinel to owner_requirements_updated
- e2e: drop owner_notes from clearMachineField union
- tests: drop ownerNotes assertions across unit + integration suites

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings June 26, 2026 15:18
@vercel

vercel Bot commented Jun 26, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
pin-point Ready Ready Preview, Comment Jun 26, 2026 3:19pm

Request Review

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants