Review: API Boards + Board Items -- 12 endpoints

Verdict: APPROVED

Template Completeness

• [x] Type -- Feature
• [x] Lineage -- decomposed from paldocs#51, depends on #49 and #57
• [x] Repo -- ldraney/paldocs
• [x] User Story -- MCP layer needs Rails board endpoints
• [x] Context -- sub-ticket 2, 12 tools listed with endpoint mapping
• [x] File Targets -- 3 files to create/modify, 3 files to avoid
• [x] Feature Flag -- none (additive API routes)
• [x] Acceptance Criteria -- 5 criteria
• [x] Test Expectations -- request specs, integration, response shape comparison
• [x] Constraints -- as_json, no jbuilder, match pal-e-docs shape
• [x] Checklist -- 7 items
• [x] Related -- project, story, arch, upstream/sibling/downstream

Traceability

• [x] story:consolidation label -- story-paldocs-consolidation note exists, listed on project-paldocs user-stories section
• [x] story note verified -- found in project-paldocs user-stories section
• [x] arch:rails-api label -- arch-rails-api note exists (architecture type, active status, project paldocs)
• [x] arch note verified -- arch-rails-api lists Api::BoardsController and Api::BoardItemsController as components
• [x] Forgejo issue -- paldocs#58, open

File Targets

• [x] app/controllers/api/boards_controller.rb -- to be created. api/ directory does not exist yet (depends on #57 creating it). Correct.
• [x] app/controllers/api/board_items_controller.rb -- to be created. Same dependency. Correct.
• [x] config/routes.rb -- exists. Currently no api namespace; #57 will add it. Correct.
• [x] app/controllers/api/base_controller.rb -- listed as "should NOT touch." Does not exist yet; #57 will create it. Correct.
• [x] app/models/ -- listed as "should NOT touch." Models already exist (BoardItem model confirmed; Board is a Note, not a separate model). Correct.

Repo Placement

Dependencies

• paldocs#49 (schema ownership transfer) -- in_progress on board. Must complete first so structure.sql exists.
• paldocs#57 (API namespace + Notes controller) -- backlog on board. Must complete first to create api/ directory, base_controller, and api namespace in routes.
• Both dependencies are correctly documented in the issue Lineage and Context sections.
• Sibling: paldocs#59 (projects/repos/tags/search API) -- independent, no blocking relationship.
• Downstream: paldocs#54 (new MCP server) -- blocked by this ticket. Documented.

Acceptance Criteria

Blast Radius

• No existing API controllers to conflict with (api/ directory does not exist yet).
• Existing UI routes for boards and board_items (show, update) are in the non-namespaced routes -- no collision risk with /api/ namespace.
• BoardItem model uses Note as board (class_name: "Note", foreign_key: :board_note_id). The implementing agent must query Note records for board CRUD, not a Board model. The arch note documents this correctly.
• Board sync logic from pal-e-docs needs replication -- agent should reference pal-e-docs source for sync behavior.

Decomposition Assessment

Recommendation