**Goals:**

* Evaluate how much of the existing Boards codebase we can Begin of the insertionre-use,End of the insertion Begin of the deletion re-use –End of the deletion with the objective of Begin of the insertionshippingEnd of the insertion Begin of the deletion **shippingEnd of the deletion user-facing features Begin of the insertionfaster. ForEnd of the insertion Begin of the deletion much faster**: inEnd of the deletion this Begin of the insertionspike, the concrete target isEnd of the insertion Begin of the deletion case,End of the deletion a Begin of the insertionnarrow but eventually shippable React subsetEnd of the insertion Begin of the deletion rudimentary UIEnd of the deletion for status mapping (see Begin of the insertion#71104).End of the insertion Begin of the deletion <mention class="mention" data-id="71104" data-type="work_package" data-text="#71104">#71104</mention> )End of the deletion

* Begin of the insertionContinueEnd of the insertion Begin of the deletion **ContinueEnd of the deletion evaluating Begin of the insertionClaude and other agentsEnd of the insertion Begin of the deletion Claude**End of the deletion for development tasks, with a particular emphasis Begin of the insertionon:End of the insertion

* Begin of the deletion onEnd of the deletion well-tested, production-quality code

* getting to know the Begin of the insertionFigmaEnd of the insertion Begin of the deletion Angular CLIEnd of the deletion MCP for Begin of the insertioncode generationEnd of the insertion Begin of the deletion Angular tasks.End of the deletion

* Begin of the insertionLearnEnd of the insertion Begin of the deletion **LearnEnd of the deletion Primer Begin of the insertionReact,End of the insertion Begin of the deletion React** -End of the deletion and evaluate how it Begin of the insertioninteroperatesEnd of the insertion Begin of the deletion interopsEnd of the deletion with Begin of the insertionPrimer ViewComponents. Also evaluateEnd of the insertion Begin of the deletion Primer&#39;s View Component implementation. Also,End of the deletion how we might Begin of the insertionhedge towardEnd of the insertion Begin of the deletion be able to &quot;hedge&quot; and take advantage ofEnd of the deletion the React library given PVC&#39;s Begin of the insertioneffectiveEnd of the insertion Begin of the deletion effective.End of the deletion deprecation. _This should feed into discussions at Begin of the insertiontheEnd of the insertion D-Team Begin of the insertionoffsite._


**Scope for this spike:**

* Keep the initial shippable subset intentionally narrow: support `free` boards and `action` boards with `attribute == "status"` in the React implementation.End of the insertion Begin of the deletion offsite!_End of the deletion

* Begin of the insertionKeep unsupported board types such as version, assignee, subproject, and subtasks on the existing Angular path for now.

* Focus on proving that the React path can be made safe, testable, and incrementally shippable by reusing existing board semantics for filters, ordering, status transitions, and existing smoke-test coverage.

* Defer broader board-type parity to follow-up work once the support boundary and shared abstractions are in place.End of the insertion Begin of the deletion <br>End of the deletion


Begin of the insertion**Constraints:**End of the insertion Begin of the deletion **Constraints**:End of the deletion

* Spend minimal human dev hours on this until we get stakeholder consensus on future frontend architecture and framework choices.

* Keep a Turbo Boards rewrite on the table.

* Use existing UI components, albeit the React implementations thereof.

* Begin of the insertionMake the spikeEnd of the insertion Begin of the deletion BeEnd of the deletion good enough to be shippable Begin of the insertioneventually; do notEnd of the insertion Begin of the deletion (eventually) - don&#39;tEnd of the deletion create something completely Begin of the insertionthrow-away.


**Non-goalsEnd of the insertion Begin of the deletion throw-away (i.e. not &quot;vibe coded&quot;) _This may be considered an anti-patternEnd of the deletion for Begin of the insertionthis spike:**

* Port all board types to React.

* Resolve the long-term frontend architecture decision for Boards.

* Replace the existing Angular implementation for unsupported board types.End of the insertion Begin of the deletion spikes, but there are already a couple open GitHub Pull Requests that show React integration that can be considered throw-away._End of the deletion