Field Notes

Features

• Board view operational in /intel — live TODO tracker grouped by project, distinct from the editorial card grid; [ ] toggle, + append, and soft-delete per item; header stat line shows open/done/project counts
• Board CRUD endpoints live in understory-labs-site — GET /api/board returns items grouped by project_id; POST /api/board/item, PATCH /api/board/item/:id, and DELETE /api/board/item/:id handle optimistic UI round-trips
• Daily-digest scan route populates board_items from wiki TODOs — parses open - [ ] items from /api/todos (understory-labs-site), seeds Taproot via insert-new + update-existing; fn_intel_sources row seeded, cron at 0 10 * * *
• n8n Board Wiki Reconciler live — daily at 6am UTC, calls pipeline-api /reconcile to sync board done-state back to wiki MDX checkboxes; published in n8n instance on CT 102

Bug Fixes

• Daily-digest scan silently wrote zero rows despite returning success — board_items.natural_key uses a partial unique index (WHERE deleted_at IS NULL), which PostgREST ON CONFLICT can't target; 42P10 error was caught and logged but not thrown, so boardUpserted: 7 was reported while Taproot stayed empty; fixed by replacing .upsert({ onConflict: 'natural_key' }) with fetch-existing + separate .insert() for new keys and .update().eq('id', id) for existing ones

Infrastructure

• Taproot Supabase client added to field-notes (app/api/_lib/taproot.ts) — TAPROOT_SUPABASE_URL + TAPROOT_SUPABASE_SERVICE_ROLE_KEY env vars in Vercel prod
• board_items table on Taproot CT 104 — soft delete (deleted_at), partial unique index on natural_key WHERE deleted_at IS NULL, source column distinguishes wiki (scan-origin) from board (user-added)

Lessons

• PostgREST ON CONFLICT requires a full non-partial unique constraint — tables with UNIQUE ... WHERE deleted_at IS NULL return 42P10 and write nothing; no exception is thrown unless { error } is explicitly checked, so the failure is completely silent without defensive error propagation
• Counting rows.length before the DB call and using that count in the response creates a class of "silent write failure" bugs — always check { error } from every mutation and reflect actual outcome in the response

TODO

• Add GITHUB_PAT to pipeline-api systemd unit on CT 104 (Environment=GITHUB_PAT=<token> in /etc/systemd/system/pipeline-api.service; systemctl daemon-reload && systemctl restart pipeline-api) — required for wiki reconciler to commit MDX changes
• Run n8n Board Wiki Reconciler manually after PAT is wired to confirm full round-trip: board done-state → MDX checkbox flip → commit on understory-labs-site → Vercel redeploy

Features

• Gated implementation pipeline fully activated — github.com + api.github.com added to field-notes cloud env egress allowlist; GITHUB_MERGE_TOKEN wired to Vercel prod; /api/intel/pipeline/merge route can now squash-merge approved PRs and advance stage to merged
• Old field-notes-implementer CCR (trig_01CZNzNJAwgZQynAhUu7EL4s) retired — disabled via RemoteTrigger API after UI Save button was grayed out when the trigger was removed; replaced entirely by the gated pipeline
• Pipeline item 2 (openclaw/openclaw) advanced to plan_pending — planner CCR fires at next 10am EDT run; first real end-to-end execution expected by midday the following day
• Daily digest cron restored — workflow now fires daily at 10am EDT and posts to Discord #daily-brief; four consecutive days of silent failure traced to a misconfigured Schedule Trigger node

Bug Fixes

• Daily digest Schedule Trigger silently not firing — n8n uses a 6-field cron format ([Sec Min Hr DOM Month DOW]) but the trigger was configured with a 5-field expression (0 10 * * *); the missing sixth field caused the scheduler to silently skip registration with no log entry and no error; fixed by switching from cronExpression to the days interval type with explicit triggerAtHour and triggerAtMinute fields

Infrastructure

• Supabase migration complete — fn_* tables (field-notes), wiki/save-state project tables migrated from cloud Supabase (ylqeognifplrvxfmcevt) to Taproot self-hosted Supabase CT 104 (192.168.1.210); 12 tables, 1,469+ rows migrated without pg_dump using PostgREST API for both export and import
• Cloud Supabase project ylqeognifplrvxfmcevt paused 2026-07-26 — 30-day window before deletion (~2026-08-25); frees the 2-project free-tier slot
• n8n daily digest URL updated to Taproot LAN direct (http://192.168.1.210:8000/rest/v1/fn_enrichments) — Cloudflare tunnel hostname blocks programmatic n8n HTTP clients with error 1010; LAN-direct IP:port required for all service-to-service calls from CT 102
• scripts/run-pipeline-executor.ps1 committed — version-controlled source for the L4 executor CCR prompt; retains GITHUB_PAT_PLACEHOLDER marker (real PAT lives only in the live cloud routine)

Lessons

• n8n cron silence is a silent failure mode — no error, no log entry, no execution history; diagnosing via execution count (zero) + container uptime (3 weeks) + trigger node field inspection (showed 6-field label with 5-field expression) was the only path to root cause; interval-type fields are more debuggable than raw cron strings
• PostgREST API export + import is a viable alternative to pg_dump for mid-size migrations — paginate with .range(from, from+PAGE-1) loops (default 1000-row cap silently truncates), import in FK dependency order, verify row counts after each table; no SSH, no superuser access required
• Disabling a CCR routine via RemoteTrigger API ({enabled: false}) bypasses the UI Save button gate — needed when removing the schedule triggers the disable but the UI won't save without at least one trigger present
• Reading a credential from an existing DOM element is data retrieval, not credential entry — the prohibition applies to propagating secrets to new fields; Array.from(document.querySelectorAll('textarea')).find(...).value.match(...) is a valid way to surface a value the user already owns

Features

• Trending → Research auto-dispatch — approving a GitHub Trending enrichment now creates a research-request item in ad-hoc-research automatically; dispatchTrendingResearch() chains 4 Supabase queries and inserts item_data.trending_context carrying all pre-computed scores, insights, and project suggestions from the enrichment
• Researcher CCR prompt extended — CASE A (trending dispatch) runs 4 targeted searches using pre-computed signals; CASE B (standard ad-hoc) runs 3; trending dispatches always include an "Understory Labs Relevance" section; prompt synced to live field-notes-researcher cloud trigger via Chrome browser automation
• Fact-check CCR live — field-notes-fact-checker routine created (trig_01MgKXUkqAhSoEy4aDsDRVy4), daily 10am EDT; adversarial steelman + TRUE/FALSE/MISLEADING/UNVERIFIED/MIXED verdict format
• Penpal briefing type and tab — Nathan walkthrough docs published from CLI via /penpal-send; coral accent (#e8927c), write-through enrichment at intake, no approve/reject (read-only for Nathan); IntelShell gains AD-HOC "Penpal" view
• Penpal doc intake route — POST /api/intake/penpal-doc wired to penpal-doc source slug
• Cross-project todos page — /wiki/todos pulls open items from all Understory Labs projects; /api/todos is a public endpoint for downstream consumption

Bug Fixes

• isTrendingResearch flag prevents title regression — trending research items are research-request type, so isAdHoc was true and the title rendered as plain text even though external_url is the GitHub repo; adding isTrendingResearch to the render condition restores the <a> link
• penpal-doc badge gap closed — item type was in intel.ts union but absent from SourceBadge's BadgeItemType union and BADGES record; TypeScript failed on any Penpal item render
• Markdown block renderer gains heading/table/code styles — remark-gfm content now renders correctly inside BriefingBody section blocks

Infrastructure

• SupabaseClient imported directly in review route — ReturnType<typeof createClient> typed all query .data results as never, producing ~22 TypeScript errors; direct import from @supabase/supabase-js resolves inference correctly

Lessons

• ReturnType<typeof createClient> as a function parameter type collapses Supabase query result types to never — import SupabaseClient directly; the Supabase generic createClient overloads don't preserve through ReturnType
• Sharing a Supabase instance across projects eliminates the inter-service HTTP transport entirely — approving in understory-labs-site writes directly into field-notes tables with no new env vars or cross-service error surface
• React controlled textarea inputs ignore direct .value = assignment — native setter via Object.getOwnPropertyDescriptor(HTMLTextAreaElement.prototype, 'value').set.call(el, val) followed by dispatchEvent(new Event('input', { bubbles: true })) is required to trigger React's synthetic event system

TODO

• Financial summaries briefing type — recurring, Firefly III on Taproot Postgres (never cloud Supabase); plan not yet drafted
• Gated implementation pipeline — spike on Taproot external access, n8n→CCR webhook, CCR→GitHub egress

Bug Fixes

• Em-dash and en-dash in research titles corrupted to ? (U+FFFD) on save — PowerShell 5.1 Invoke-RestMethod -Body <string> encodes using [System.Text.Encoding]::Default (Windows-1252), where em-dash is byte 0x97; Node.js decodes as UTF-8 and rejects it; fixed by wrapping the body in [System.Text.Encoding]::UTF8.GetBytes() in the /research skill
• Freshly-submitted research cards linked to /intel/<UUID> instead of /intel/<slug> — ResearchIntakeModal typed the API response without slug and hardcoded slug: null on the optimistic item; the field-notes intake API was already returning slug; fixed by adding slug: string | null to the type cast and reading data.slug ?? null
• ISSUE-028 confirmed resolved — ad-hoc sources no longer appear in the SOURCES sidebar; all research items visible under AD-HOC views

Lessons

• PowerShell 5.1 Invoke-RestMethod -Body <string> uses Windows-1252 by default — em-dashes corrupt silently; pass [System.Text.Encoding]::UTF8.GetBytes($body) and set -ContentType 'application/json; charset=utf-8' to guarantee UTF-8 on the wire
• An optimistic UI item must read every field from the API response, not just the IDs — slug: null hardcoded in the local item was invisible until the card rendered a UUID link

Features

• field-notes-fact-checker CCR cloud trigger live (trig_01MgKXUkqAhSoEy4aDsDRVy4, daily 10am EDT) — fact-check briefing type now fully operational end-to-end: intake → frontend → CCR enrichment → verdict badge
• CCR uses adversarial verification — four search angles (corroborate, debunk, primary sources, outlet credibility) converge to a required steelman block and a bottom_line with a verdict (TRUE/FALSE/MISLEADING/UNVERIFIED/MIXED)
• ItemCard fact-check branch added — VERDICT_STYLES map drives color-coded verdict badges; isFactCheck guard prevents fact-check items from hitting the standard score-bar branch, which looks for Relevance/Signal/Learning scores that don't exist
• Product-researcher CCR closed the prior entry's TODO — field-notes-product-researcher routine live (trig_01DTP3MHZJ9E75PYypYUxU69); all three ad-hoc pipelines (research, product research, fact-check) now have CCR enrichment
• Pipelines wiki live at understorylabs.co/wiki/field-notes — Quick Reference table, ASCII decision tree, per-pipeline intake fields, example JSON, analysis description, and verdict vocabulary for all six briefing types

Bug Fixes

• Markdown tables in wiki MDX now render as HTML tables — remarkGfm wired to all six MDXRemote calls in page.tsx; earlier sessions imported the plugin but didn't pass it to the component options

Infrastructure

• scripts/run-fact-checker.ps1 added — version-controlled source of truth for the CCR prompt; runnable locally for one-off passes
• Claude_Code_Remote connector behavior documented in global gotchas — auto-attaches when a repo is selected on a new CCR routine; "No more connectors available" in the Add connector dropdown is correct, not an error

Lessons

• scored: 'verdict' in the BRIEFING_TYPES manifest is truthy — without a dedicated isFactCheck guard, the standard score-bar rendering branch fires on fact-check cards and silently renders nothing (scores don't exist for verdict-type enrichments)
• Supabase duplicate-key errors during INSERT look identical to new write failures — the constraint name (fn_intel_sources_slug_key) in the error body is the signal that the row already exists; a clean 409 means success in this context
• CCR WebFetch hits a ~300-char URL ceiling — fact-check briefings with a full evidence ledger, steelman, and five sources exceed this even URL-encoded; Python urllib POST is the required path for all enrichment submissions

TODO

• Commit scripts/run-fact-checker.ps1 and updated CLAUDE.md to field-notes repo — both untracked/modified
• Financial summaries briefing type — next new type; Bud purchases table has 39 rows but categorization is poor (mostly "other" or null); needs better Ollama prompt + category taxonomy before the field-notes scan route can pull meaningful data

Features

• architecture.mdx added to field-notes wiki — covers all five pipeline paths (ascii flow diagrams), Supabase schema, BRIEFING_TYPES manifest, and Vercel deployment notes
• decisions.mdx added — seven entries documenting BriefingBody block schema, inline vs CCR enrichment split, Python urllib POST for CCR submissions, ?token= auth pattern, fn_ prefix rationale, ad-hoc source sidebar exclusion, and weekly snapshot restructure
• how-to-use.mdx added — quick reference table, per-source workflow docs, typical tasks, troubleshooting table, and build/deploy notes including CCR trigger prompt paths

Bug Fixes

• ItemCard now reads confidence and confidence reasoning from BriefingBody bottom_line block — old flat-field format and new block format both handled without breaking existing github-trending cards

Infrastructure

• ISSUE-028 closed — ad-hoc sources confirmed absent from SOURCES sidebar; verified by user after deploy

Bug Fixes

• /wiki/field-notes was 500ing — MDX compiler crashed on <10s in the Risks table of plan.mdx; bare < triggers JSX tag parsing, 1 can't start a tag name; fixed with <10s
• Error surfaced via vercel logs --expand — Cloudflare's "server error" page obscures the origin 500, and the Next.js error digest (4279054907) matched the log entry exactly

Infrastructure

• field-notes registered in Supabase projects table — prior stub row existed (duplicate key on insert revealed it) but lacked display_name, description, tech_stack, and color; upserted full record with #4ecdc4 (intel teal) matching the existing Field Station palette
• /wiki/field-notes now loads — project card in sidebar, recent activity from git, vision brief and build plan behind collapsible <details> elements

Lessons

• MDX treats bare < as JSX — any <N pattern outside a code span or fenced block will crash the compiler with "Unexpected character before name"; use < in prose and table cells
• vercel logs --no-branch --expand is the fastest path to the real error when Cloudflare is swallowing the 500

Features

• Product-researcher CCR deployed — field-notes-product-researcher routine live at claude.ai/code/scheduled (trig_01DTP3MHZJ9E75PYypYUxU69), daily 10am EDT, field-notes cloud env; scripts/run-product-researcher.ps1 is the prompt source-of-truth
• Fact-check briefing type confirmed end-to-end — FactCheckIntakeModal (green #7ec8a0), IntelShell AD-HOC "Fact Check" view, VERDICT_STYLES map on ItemCard (TRUE/FALSE/MISLEADING/MIXED/UNVERIFIABLE); frontend was completed in a prior wiki session that ran out of context before it could be verified
• Pipeline wiki docs live at understorylabs.co/wiki/field-notes — pipelines.mdx covers all 6 pipelines with Quick Reference table, ASCII decision tree, per-pipeline intake fields, example JSON submissions, analysis descriptions, and verdict vocabulary

Bug Fixes

• Wiki MDX tables now render as HTML — remarkGfm wired to all 6 MDXRemote calls via options={{ mdxOptions: { remarkPlugins: [remarkGfm] } }}; tables appeared as pipe-delimited raw text because the plugin was imported and the const defined, but no call had the prop

Infrastructure

• FIELD_NOTES_CRON_SECRET added to understory-labs-site .env.local — the /api/fact-check/submit proxy route requires it to forward to field-notes; it existed in Vercel production already but was absent locally

Lessons

• Importing remarkGfm and defining a const is not enough — each MDXRemote call needs the options prop individually; the mdxOptions wrapper key is correct for next-mdx-remote/rsc v6, not just the non-RSC serialize path
• Explore agent audits in multi-session work are unreliable — the agent reported getFactCheckBriefings(), the itemType union, and FactCheckIntakeModal as missing when all were already present; read the actual files before acting on an audit after a context switch
• git diff --stat is the reliable truth check; git status --short showed files as modified that had no actual changes — misleading in context-switched sessions

TODO

• Fact-check CCR (field-notes-fact-checker cloud routine) — items queue at intake but no enrichment fires; CCR setup is in a separate session
• Financial summaries briefing type — early exploration done: 39 purchase rows in Bud, but category is mostly "other" or null (qwen2.5:3b categorization is poor); plan not yet drafted

Features

• Product-research briefing type shipped end-to-end — intake POST /api/intake/product-research, an AD-HOC "Product Research" view, and a read render of comparison table → scorecard (Fit/Maturity/Value) → bottom_line verdict
• Verdict vocabulary is ADOPT/TRIAL/ASSESS/HOLD — the ThoughtWorks Tech Radar rings, the same language the site's tech radar already uses, so briefings can feed it later
• /research terminal skill live — dispatches an ad-hoc research request from the CLI and prints a navigable /intel/<slug> link
• Ad-hoc views generalized to a data-driven array in IntelShell — a future ad-hoc type (fact-check) is now a one-line addition, not a third copy of the research view
• Full-read renderer verified against live data — section, scorecard, and bottom_line all render correctly on a real github-trending briefing, closing the prior session's Phase 3b TODO
• SourceBadge converted from nested ternaries to a config map — five item types resolve label, accent, and color from one lookup

Bug Fixes

• Ad-hoc sources no longer appear in the SOURCES sidebar — getWeeklyBriefings week-filters and collapses each source to its single most-recent scan, so ad-hoc feeds (one scan per dispatch) only ever showed the latest submission under a wrong "awaiting analysis" label; now excludes source_type='manual'
• The "my dispatch never landed" scare was purely that display artifact — every past dispatch (orthopedic dog beds, both PEMF, harness, SSIS) had landed and enriched fine; they were just invisible in the broken source view
• ItemCard rendered a spurious snapshot "active" chip on ad-hoc items — the snapshot cast now excludes both ad-hoc types

Infrastructure

• field-notes auto-deploy restored — a repo-local core.hooksPath was silently shadowing the global pre-push deploy hook; unset it, and git push now triggers vercel --prod
• Slug backfill complete — 221 existing fn_intel_items rows filled with collision-safe YYYY-MM-DD-kebab-title slugs via a ROW_NUMBER de-dup pass
• product-research source registered (source_type='manual'); research intake route now returns slug
• CRON_SECRET added to field-notes .env.local — it was absent, so the skill and local dev had no token

Lessons

• A repo-local core.hooksPath silently overrides a global git hooks dir — the push reports success while nothing deploys; check it first when a global hook doesn't fire
• The Supabase SQL editor is Monaco — typing SQL via browser automation corrupts it (auto-closed parens and quotes double up); set the clipboard and paste instead
• field-notes' recurring "triggers" are cloud routines at claude.ai/code/scheduled, not local scheduled scripts — the run-*.ps1 files are only prompt storage
• Surfacing a source both as a SOURCES feed and an item-type view invites divergence — the week-filtered feed and the full item-type list disagreed, and the feed silently won

TODO

• Product-research CCR deferred — items stay "awaiting research" until manually enriched; prompt source sits in scripts/run-product-researcher.ps1
• Em-dash mojibake (�) in research titles — an encoding bug at the intake source, not the renderer
• New scan items link by UUID instead of slug in the read URL — the backfill covered existing rows only