Cleaning Dead Routes, Fixing Development Sheets, and Connecting Incidents in a NestJS‑ClickUp‑Notion CRM

<h1> Cleaning Dead Routes, Fixing Development Sheets, and Connecting Incidents in a NestJS‑ClickUp‑Notion CRM </h1> <p><strong>TL;DR:</strong><br><br> I removed unused routes from <code>DevelopmentsController</code>, fixed the wrong controller reference in <code>VentasController</code>, added the missing <code>create</code> flow for development sheets in Craft, and wired up the incident API to pull data from ClickUp. These changes eliminate runtime errors, streamline the API surface, and sync incident data with development tickets.</p> <h2> The Problem </h2> <p>The CRM API was leaking several bugs that surfaced during integration tests and in production:</p> <ol> <li> <strong>Dead routes</strong> – <code>DevelopmentsController</code> still exported endpoints that never existed in the database schema, leading to 404s and unnecessary validation overhead.</li> <li> <strong>Wrong controller reference</strong> – The <code>VentasController</code> tried to call a method on the <code>DevelopmentsController</code> that had been renamed, causing a <code>TypeError: undefined is not a function</code>.</li> <li> <strong>Missing development sheet creation</strong> – When a new development record was inserted, the corresponding Craft sheet was never created, breaking downstream analytics.</li> <li> <strong>Fake incident cards</strong> – The front‑end rendered seven placeholder incident cards that never mapped to real data, confusing users and bloating the UI.</li> <li> <strong>Docs out of sync</strong> – The <code>CLAUDE.md</code> and <code>CLAUDE_CODE_CONTEXT.md</code> files referenced an old commit hash (<code>08ed379</code>) instead of the current one (<code>bad3d3b</code>).</li> </ol> <p>These issues were surfacing as runtime errors and confusing UI states, so I needed a clean, reproducible fix.</p> <h2> What I Tried First </h2> <p>I started by inspecting the stack traces from the failing tests. The first error was a 404 from the development endpoints, so I ran a quick grep:<br> </p> <div class="highlight js-code-highlight"> <pre class="highlight shell"><code><span class="nb">grep</span> <span class="nt">-R</span> <span class="s2">"DevelopmentsController"</span> <span class="nt">-n</span> apps/api/src/ventas </code></pre> </div> <p>This revealed that the controller had a <code>@Get('dead-route')</code> that never matched any database field. I initially thought to just comment it out, but that would leave an orphaned route in the Swagger docs. I then tried to delete the route manually, but the compiler complained about missing imports.</p> <p>Next, I looked at the <code>VentasController</code> error. The stack trace pointed to a call to <code>this.developmentsService.create()</code> that no longer existed. I patched the service with a dummy method to bypass the error, but that didn’t solve the underlying mismatch.</p> <p>For the missing sheet creation, I added a temporary console log after the database insert to confirm that the request reached the controller. It did, but the subsequent call to <code>CraftService.createSheet()</code> was never made because the function was never invoked.</p> <p>Finally, I checked the front‑end. The <code>page.tsx</code> had a hard‑coded array of seven cards. I removed them manually, but the UI still showed placeholders because the state was still pulling from an old endpoint that returned an empty array.</p> <h2> The Implementation </h2> <p>Below is a walk‑through of the concrete changes I made, including the exact file diffs and architecture decisions.</p> <h3> 1. Cleaned Dead Routes in <code>DevelopmentsController</code> </h3> <div class="highlight js-code-highlight"> <pre class="highlight diff"><code><span class="gd">- import { Body, Controller, Delete, Get, Param, Patch, Post, Query, UseGuards } from "@nestjs/common"; </span><span class="gi">+ import { Body, Controller, Delete, Get, Param, Patch, UseGuards } from "@nestjs/common"; </span></