Drop the Comp AI CRM acknowledgement

Nothing in PIG derives from that repository. The fact model, the leased
agent task queue and the `agentBrief` field are our own designs, and MIT's
attribution condition reaches copied source, not ideas — so the credit was
a courtesy that misstated where this code came from.

The one line worth keeping was never a credit: AGENTS.md's rule against
lifting component files out of somebody else's repo. It is restated
generically, and the shadcn-from-upstream guidance stays.

Buzz keeps its NOTICE entry.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

docs/build-plan.md

@@ -152,31 +152,29 @@ any native mobile application.
 
 ---
 
-## On borrowing from Comp AI CRM
+## On the component library
 
-Their repo (MIT) was cloned and inventoried early on, and three findings shaped
-the plan. All three have since been acted on.
+Three gaps were identified in an early review of the front end. All three have
+since been acted on.
 
-**Their component library was far deeper — 68 primitives to our 9 at the time.**
-PIG now has 22, including the ones that mattered: `data-table`, `command`,
-`sheet`, `drawer`, `sidebar`, `form`. The agent-chat compositions
-(`message`, `reasoning`, `thinking-indicator`) were rebuilt rather than copied,
-inside `PiggyChat.tsx`.
+**The primitive set was too thin — 9 at the time.** PIG now has 22, including
+the ones that mattered: `data-table`, `command`, `sheet`, `drawer`, `sidebar`,
+`form`. The agent-chat compositions (`message`, `reasoning`,
+`thinking-indicator`) are ours, written inside `PiggyChat.tsx`.
 
-**`SourcedValue` / `Provenance` was worth adopting outright** — a dotted
-underline on any agent-derived value, with a tooltip carrying the claim, the
-reasons, when it was observed and the source URL. PIG already held that data in
-`facts` and surfaced none of it. It does now.
+**`SourcedValue` / `Provenance` had to exist** — a dotted underline on any
+agent-derived value, with a tooltip carrying the claim, the reasons, when it was
+observed and the source URL. PIG already held that data in `facts` and surfaced
+none of it. It does now.
 
-**We were ahead of them on mobile, not behind**, and the ratio has held: PIG is
-63 `.tsx` files with safe-area handling, a bottom tab bar, a sidebar Sheet and a
-hard rule that no route may scroll sideways at 393px. Their app is effectively
+**Mobile is a lead, and the ratio has held:** PIG is 63 `.tsx` files with
+safe-area handling, a bottom tab bar, a sidebar Sheet and a hard rule that no
+route may scroll sideways at 393px. Most tools in this category are effectively
 desktop-only.
 
-**Do not copy their component files.** Most are shadcn/ui originals, which are
-MIT and designed to be installed from upstream — take them from source, where
-they are canonical and current. Borrow the compositions as ideas, and credit in
-`NOTICE` as already done.
+**Where a primitive is a shadcn/ui original, install it from upstream**, where
+it is canonical and current — not lifted out of somebody else's repository.
+Compositions we write ourselves.
 
 ---