augment-it/issues
- Path
- issues/index.md
Issues
- A component test whose fixture is simpler than its call sites - Selector–Menu’s suite was green while both of its first two adopters were broken in exactly the way its header promises to prevent.
- A failed deploy is silent, so nothing watches production after merge - Every frontend Docker build failed for twelve days unnoticed: the old container keeps serving and the health check keeps passing.
- A silently ignored alias pointed a verification probe at production - rsbuild accepts source.alias and ignores it. Three agents rendered live data believing it was a fixture; one wrote a file into client corpus.
- Augment Transformations Not Reliably Persisting — Hand-Curated Field Edits and Whole-Row Augmentations Are Disappearing Across Record-Set Versions - 98 hand-curated URLs across 45 records with no save or promote affordance — only the row-store’s auto-persisted JSON keeps them alive.
- Capability Gaps Surfaced by the First Triage Co-Pilot Run — One Collective Ledger, Not Five Tickets - Five gaps from the first triage run — including direct SurrealDB writes whose string-typed ids silently failed to join their org rows.
- Changelog entries duplicated across augment-it/changelog/ and content/changelog–laerdal/ - Eleven backfilled augment-it changelog entries currently live in two places. Either location can be the source of truth — but right now both are, and updates have to be made twice.
- Concurrent agent searches queue into a search-results column — fire many, deal with them as they come - Agent searches run 60–210s and each one hijacks a single column. Wanted: a rightmost queue where every fired search appends its own card.
- Corpus adds don’t fetch metadata — and the row gives no cue either way, and there’s no inspector to see or fix it -
organization.corpus.addwrites url, kind, and domain then stops — the Jina metadata fetch never fires, and nothing on the row says so. - Corpus items aren’t visible on person cards — and corpus coverage across entities is hard to assess anywhere - The person card says ‘Corpus items 3’ and shows nothing — the operator can add a fourth without ever seeing the three that exist.
- Crawl progress is a black box — ‘crawling the web, this takes a minute…’ needs traces the operator can watch - The model narrates as it crawls —
extractTextskips straight past it to the final answer, so the operator gets a minute of ellipsis. - Crawl replies can be lost — the eternal ‘crawling…’ spinner (no client timeout, reconnect-dropped invokes, tight dispatch ceiling) - The Curry Foundation crawl finished in 87s and the tab spun forever: no client deadline, reconnect-dropped invokes, a 300s ceiling.
- The crawl’s search substrate is fixed to Anthropic web search — the operator expected to choose - The manual 🔍 has a provider palette;
organization.crawlis hardwired to Anthropic’s server-side web_search with no dial and no label. - Domain type is ambient state, so a failed workspace load hides every corpus - humain-vc opened the Corpora Curator and saw ‘strategy’ and ‘No corpora yet’ — it has theses, and plenty of them. One guessed value at load time silently filtered the whole surface, and the same symptom was debugged out once already on 2026-07-07.
- Every remote hardcodes the workspace WebSocket to localhost — Org Workbench loads no data on augment.didi.sh - Sixteen remotes dial
ws://localhost:3001/wswith no env read. On prod that points at the visitor’s own laptop, so the socket showsclosedand the roster never fills. - Fetch full content clobbers the operator’s metadata — resets the title to a URL approximation -
fetchSourceContentnever consulted the saved title, so Jina’s guess — or the raw URL on failure — overwrote what the operator typed. - Switching flows from the Flows popdown doesn’t surface the new flow’s stage — a rotation-step click is required - Switching flows flips the pill but leaves the stage blank until a step-bubble click. Only tabs with persisted layout state reproduce it.
- Funder Corpus First Session Failed — 75 markdown files across 15 of 96 funders, 81 records unprocessable, hours spent layering filters on stale data instead of producing clean fresh data, rebuild against the goals spec exists in code but was never validated against a real pack fire because the session ended - Six hours produced 75 corpus files across 15 of 96 funders — 81 records still have nothing. This is the failure-mode list for morning-self.
- Funder↔strategy is tags for now — whether it deserves a real edge is deferred - 140 strategy tags landed on 69 funders, but a tag can’t carry evidence counts, gift sizes, or recency. The edge question comes due later.
- Grilling on the DB Resolver — questions to settle before v0.0.0.2 / v0.0.0.3 - Three decisions before v0.0.0.2: where the join key lives, whether a slug can be renamed safely, and whether opportunities reopens Decile.
- Header polish — the FLOW label and shell suffix have outlived their jobs, and the chat toggle sits on the wrong side - Four findings from the first production walk-through — including a chat toggle on the right that opens a rail pinned to the left.
- Issue: How People, Organizations, and Their Relationships Actually Enter SurrealDB - Not a bug — a verified trace of the canonical write path, because the DB already does more than the UI or the operator’s memory shows.
- Invokes survive reconnects — the claim protocol closes the eternal-spinner root cause - Two crawls finished server-side while the tab spun forever. Pending invokes now survive a socket drop and re-attach by id via claim frames.
- Issues raised by the migration subagent while converging request-reviewer - Findings surfaced while doing something else. Raised, not chased — the diff stays clean and the finding stays reviewable.
- Jina metadata parser is blog-only — needs two profiles + fuzzy routing (academic sources lose their date/publisher) - The parser only reads OpenGraph keys, so scholarly sources lose date and publisher to
citation_*/dc.*/prism.*it never looks at. - List rows show hostname only — the path is hidden, so same-domain entries are indistinguishable -
AdditiveList’shost()drops the pathname, so two Gates Foundation links both render asgatesfoundation.organd can’t be told apart. - Live/not-live indicator tooling — parts of the UI feel dead, and there’s no single view that says whether everything is actually working - Five distinct failures — dead remote, dead socket, dead service, no refresh, unwired button — all present to the operator as one dead click.
- Merging organizations or people — when two objects turn out to be the same entity, dedupe non-destructively - Two rows are sometimes the same entity and nothing merges them — no edge re-pointing, no list union, no slug absorbed into
aliases[]. - Move the rest of the app to remote hosting — prod still falls back to localhost for every undeployed remote - 12 micro-frontends are hardcoded to
http://localhost:3XXXin the prod shell, so augment.didi.sh fetches them from the visitor’s machine. - No component library — the UI is improvised per-remote instead of component-based, and it’s starting to show - Fourteen remotes improvised their own UI, so status pills and candidate pickers now exist in parallel dialects. The bill is arriving.
- No test coverage — TDD keeps getting deferred, despite being exactly the right fit for agentic development - Agents rewrite this codebase with zero automated tests — and the iterate-until-green loop is exactly what agents are best at. Pick a runner.
- No user visibility into state — the app needs a State-Inspector surface - State lives in five places and none are inspectable from inside the app — nothing shows which remote currently believes what.
- OfficialPulse URLs Appear as Junk in Promoted Versions — operator believes promote v6 → v7 → v8 wrote bad data into the array column; audit shows promote is clean and v6 itself already contained every URL - Promote added nothing — v5 through v8 carry identical 122-URL arrays. The new renderer just made them visible, and no UI can remove one.
- One stuck message kills a NATS subject until restart —
domain.list: timeoutand the sequential handler loop - Every handler indomains.tsconsumes its subject with afor awaitloop, so one unsettled request blocks the subject until a restart. - Org Workbench in a narrow pane — the roster doesn’t collapse, and the org card’s contents spill out of their container - In a narrow pane the roster keeps its 300px and the card’s link rows overflow — the flexbox
min-width: autotrap, twice. - The Org Workbench can’t create an organization — and creation must sit behind a ‘be sure there is no match’ gate - The workbench can only find orgs that exist. Creation must sit behind the same show-every-match gate that already governs adding a person.
- Parent-Child Nested Organizations Are Not Modeled — Initiatives, Funds, and Sub-Orgs Have Nowhere Canonical to Hang -
upmobility-foundation-urban-institutewelds a parent org to its initiative, so triaged content has no honest folder to land in. - A person’s bio page on another org’s site is an affiliation signal, not just an identity link — the UI should offer the promotion - A bio on another org’s domain is three facts — identity link, affiliation evidence, observation. The card captures one and drops two.
- Issue: Person · DB Resolver UI needs to accommodate multiple organizations per person -
person-db-resolverresolves one org per row, but Lincoln Ellis’s bio names four — no way to add an Nth without re-running the row. - Personal-link observations need named query lenses — without them, an accumulating fact log goes uninspected -
has_personal_linkobservations carry rich qualifiers and no queries. One thought leader can contribute 50+ before anyone can look. - Pulse streams need an editable kind and a user-facing name — ‘Today’s Credentials’ is not an ‘updates_index’ - The operator can neither fix a stream’s inferred kind nor record its name —
media_streams[]has no title field for Today’s Credentials. - Refactoring for API Speed — a single-user app should boot in milliseconds, not a minute - Measured: shell mount to workspaces ready is ~543ms. The perceived minute was a stale deploy plus remotes hanging on
localhost:3XXX. - Relation kinds are inverse pairs — one stored string can’t speak from both seats - NextLadder is funded_by Ballmer Group; Ballmer Group is funder_of NextLadder — the same edge needs a different kind string per perspective, and today only one pair is special-cased in a read-time map.
- Search & Add’s invokes never reach the workspace — the pane hangs at ‘searching…’ while every backend rung is green - SearXNG answers,
search.fireanswers, the org card loads — yet the 🔍 pane hangs forever. The frame dies inside the client transport. - The search column holds stale results — a new agent search doesn’t reload it - The team crawl bypasses the Search & Add envelope, so the column sits frozen on the last search’s candidates, masquerading as current.
- Search Providers as First-Class — Stand Up SearXNG as the New Default for Social Packs; Tavily Stays as a Peer; Per-Row Iteration as the Workflow We’re Building Toward - Tavily is a content-RAG index — wrong substrate for social-profile pages. The fix isn’t a swap — it’s making provider plural per-fire.
- Session expiry turns the app into a zombie — the 12h JWT dies mid-use, the UI stays up, and every invoke times out - The
didi_sessioncookie lives 30 days, the JWT inside ~12h, and nothing calls/api/session/refresh— the transport 4401-loops at 2/sec. - Some records show empty corpus in the Sort & Filter Lens despite per-funder directories existing on disk — the lineage join is healthy but the workspace-service capability has no timeout override (defaults to 5000ms), the content-ingest handler processes requests serially, and each call walks every funder directory under clients/
/corpus/, so late requests in the 96-row fan-out time out and the lens swallows the error silently; the durable fix is to make corpus_funder_slug (a column the records sheet already populates) the primary join key, which limits each call to one small directory and dissolves the timeout race — this supersedes the originally-proposed corpus-overrides.yaml because the override surface is now the records-sheet cell - NoCAPABILITY_TIMEOUTS_MSentry forcorpus.list_for_record— 96 parallel calls hit the 5000ms default and the lens swallows the error. - Structural invariants live in prose, so sweeps stop halfway and nothing notices - Three units have now been found whose typecheck had never once passed. Each was found by accident, five weeks apart, by someone tidying something else.
- Tag input swallows commas into one mega-tag — commas should split into separate tags -
toDashedsplits on every non-alphanumeric, so commas behave like spaces and three intended tags fuse into one mega-tag. - Team-crawl accept drops the crawled links and leaves the staged row — double-save risk -
person.applywriteslinkedin_profile_urlas a scalar only, so accept discards the crawl’s links — and the staged row lingers. - The federation has no layout layer, so seven of its eight deviations are about placement - The design system standardised everything that goes inside a box and nothing about the boxes. Consumers keep their freedom for now — deliberately, and on the record.
- Tokens landed, components didn’t — the UI needs an overhaul, and the drift linter can’t see the problem - 19 of 20 apps consume the theme package; shared-ui ships exactly two components. Every remote hand-rolls its own buttons, pills, and empty states against shared colours.
- Troubleshooting UI for Official Blogs — The Bundle Fire Path Doesn’t Fit the Flow That Was Built for Prompt Templates - Bundles fire end-to-end, but the Flow assumes every fire routes through a prompt template — so every step past 2 is wrong for a bundle.
- Troubleshooting workspace ↔ DB state alignment — humain-vc’s corpora don’t load, and the canonical layer holds fewer than the operator created - The humain-vc workspace renders empty-or-wrong corpora while the canonical layer itself holds fewer humain-vc domains than the operator remembers creating — four suspects, each with a discriminating signature.
- Workspace + corpora connection is slow-to-hanging, and the auth token won’t persist - The Corpora Curator sits at ‘connecting…’ and the workspace switcher at ‘loading…’ — corpora never arrive — while the didi session drops within a minute of signing in, forcing a re-login. Two symptoms that most likely share one root cause.