Kinds / Canonical
issues/
The winding path through a hard bug, written down so nobody retraces it.
121 files · 23 projects
augment-itai-labs56
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 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.
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.
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.
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.
Every remote hardcodes the workspace WebSocket to localhost — Org Workbench loads no data on augment.didi.sh
Sixteen remotes dial `ws://localhost:3001/ws` with no env read. On prod that points at the visitor's own laptop, so the socket shows `closed` and the roster never fills.
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.
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.
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.
One stuck message kills a NATS subject until restart — `domain.list: timeout` and the sequential handler loop
Every handler in `domains.ts` consumes its subject with a `for await` loop, so one unsettled request blocks the subject until a restart.
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:3XXX` in the prod shell, so augment.didi.sh fetches them from the visitor's machine.
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.
Fetch full content clobbers the operator's metadata — resets the title to a URL approximation
`fetchSourceContent` never consulted the saved title, so Jina's guess — or the raw URL on failure — overwrote what the operator typed.
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.
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.
Parent-Child Nested Organizations Are Not Modeled — Initiatives, Funds, and Sub-Orgs Have Nowhere Canonical to Hang
`upmobility-foundation-urban-institute` welds a parent org to its initiative, so triaged content has no honest folder to land in.
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`.
Search & Add's invokes never reach the workspace — the pane hangs at 'searching…' while every backend rung is green
SearXNG answers, `search.fire` answers, the org card loads — yet the 🔍 pane hangs forever. The frame dies inside the client transport.
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_session` cookie lives 30 days, the JWT inside ~12h, and nothing calls `/api/session/refresh` — the transport 4401-loops at 2/sec.
Tag input swallows commas into one mega-tag — commas should split into separate tags
`toDashed` splits on every non-alphanumeric, so commas behave like spaces and three intended tags fuse into one mega-tag.
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.
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.
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.
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.
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.
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.add` writes 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 — `extractText` skips 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.crawl` is hardwired to Anthropic's server-side web_search with no dial and no label.
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.
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.
List rows show hostname only — the path is hidden, so same-domain entries are indistinguishable
`AdditiveList`'s `host()` drops the pathname, so two Gates Foundation links both render as `gatesfoundation.org` and 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[]`.
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 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.
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: auto` trap, 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.
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.
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.
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.
Team-crawl accept drops the crawled links and leaves the staged row — double-save risk
`person.apply` writes `linkedin_profile_url` as a scalar only, so accept discards the crawl's links — and the staged row lingers.
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.
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.
Issue: Person · DB Resolver UI needs to accommodate multiple organizations per person
`person-db-resolver` resolves one org per row, but Lincoln Ellis's bio names four — no way to add an Nth without re-running the row.
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.
Personal-link observations need named query lenses — without them, an accumulating fact log goes uninspected
`has_personal_link` observations carry rich qualifiers and no queries. One thought leader can contribute 50+ before anyone can look.
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/<id>/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
No `CAPABILITY_TIMEOUTS_MS` entry for `corpus.list_for_record` — 96 parallel calls hit the 5000ms default and the lens swallows the error.
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.
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.
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.
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.
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.
augment-it/issues
astro-knots10
Verifying the Wikilink Resolver Migration on mpstaton-site
The migration is written, pushed, and provably identical to the rules it replaces — but nobody has watched it resolve a single real link, because the content it needs is behind two API tokens that only exist on another machine.
Astro Check Type Errors on mpstaton-site
`pnpm build` passes while `astro check` reports 8 errors — five root causes, only one of which lossless-site shares.
Documentation Gaps Blocking New Site Onboarding
The canonical markdown package has no package.json, and the reference site uses the `workspace:*` pin CLAUDE.md forbids.
Hot Reload for Raw-Filesystem Content (across astro-knots sites)
`readFileSync` content never hot-reloads — it sits outside Astro's content layer. Needs a Vite watcher AND a dev cache bypass, not either.
Nine hand-rolled frontmatter parsers, all functionally identical
One YAML bug had to be fixed nine times. The nine copies turn out to be byte-different and behaviourally identical — the drift is brace style, nothing more.
Resolving Mode Switching Across Multiple Components
Astro scopes your `[data-mode]` selector to the component, but the attribute lives on `<html>` — it never matches. `:global()` is the fix.
Scripting Across Multiple Tables in NocoDB
Links emailAccess rows to Organizations by email domain, minting orgs as needed — via the `[linkField.id]: [{id}]` update syntax.
SSH Key Passphrase Prompts - macOS Keychain Integration
The passphrase prompt returned because `~/.ssh/config` had `UseKeychain` only under `Host gitlab.com` — a `Host *` block fixes the rest.
Images in LFM render without intrinsic dimensions
Both image paths in the LFM renderer emit an <img> with no width or height, so every image will shift the page as it loads. Latent today because no changelog has images — about to stop being latent.
astro-knots/issues
content-farm7
Nudging AI search to return contextually appropriate images
The streaming pipeline silently drops Perplexity's images array — port the [IMAGE N] marker pattern the article generator already uses.
Widening (and Re-Sizing) Obsidian Plugin Modals via CSS
Modal width lives on this.modalEl, not this.contentEl — the plugin-template convention that everyone copies is why modals stay narrow.
Metafetch wraps tags array items in quotes
Metafetch re-serializes the whole frontmatter, so its quote-everything rule turns an inline `tags: [a, b]` into one quoted string.
Symlinked vault folders are invisible to the Obsidian index
Half our vault's top-level folders are symlinks into the monorepo. `vault.getAbstractFileByPath()` doesn't reliably see them, so every plugin that checks 'does this folder exist' before creating it is one symlink away from an EEXIST crash.
What to do with grab-reference — a citation-manager web stack living in the Obsidian plugin family
grab-reference turns out not to be an Obsidian plugin: it's a private 'citation-manager' pnpm workspace (web app + Prisma API + Docker) on a 2024-era toolchain. Decide its fate before spending any upgrade effort on it.
Obsidian Review Bot Feedback on Perplexed Submission
165 bot findings, all in main.ts — plus the Appendix: the PR queue died mid-fix, and the plugin description lives in three places.
content-farm/issues
ai-labs4
Splash rollup:sync fails from where the operator actually stands
`pnpm rollup:sync` errored at the ai-labs root (no such script) and inside splash/ (pnpm 12 ignored the build allowlist). Both fixed.
State-Inspector as a universal need — every ai-labs app hides its state from the people running it
No ai-labs app can answer "what does it currently believe?" — rune singletons, deck state, LangGraph FlowState, none inspectable.
The Drag in AI-Assisted Web Research — Diagnosis, Prior Art, and the Open Forks for a Source Curation Gate
AI research yields enough hallucinated sources that manual Google + Docs looks time-competitive. The drag is structural, not a prompt bug.
ai-labs/issues
cite-widecontent-farm4
Issue: Enriching the Lossless Vault's 75 Citations with Promotion's Metadata Pipeline
We ran the new canonical-source pipeline over every citation in the vault. It filled 49 reference texts and 63 publishers, and found five bugs.
Paste LLM Content drops prose structure and emits link-only citations
Paste rewrites citation tokens and nothing else — headings flatten, refs become self-referential links, and one URL gets two hex codes.
Users need to define their own citation format — the Lossless house style is hardcoded
Cite Wide hardcodes one house style across four services. Templating is the feature; centralizing the format is the prerequisite.
cite-wide/issues
perplexedcontent-farm4
Getting Claude to Respond with Research
Claude returns 60 URLs but zero per-claim citations — web_search_20260209's dynamic filter loses the attachment, so no inline markers.
Partials and preambles for perplexed templates
Mermaid rules sit in all four templates and three directives are hardcoded in TS — pull both into vault-visible partials and preambles.
Wall-clock timeout cuts off long deep-research streams
The directory-template runtime caps every stream by wall clock, so a 7,500-word deep-research draft terminated mid-sentence.
perplexed/issues
lfm4
Heading Outline Cannot Distinguish Container Headings from Document Headings
`tree.data.headings` collects a `###` inside a `> [!info]` callout as a document section — right for anchors, wrong for a table of contents.
JSR Export Map Omits the Formats Subpaths
`deno.json` declares two exports; `package.json` declares six. The four it omits are the entire code-fence format registry — so the feature 0.4.1 was built around is unreachable for every consumer that installs from JSR, which is all nine of them.
Workspace vs JSR for LFM Consumers
Why most consumer sites should pin @lossless-group/lfm to JSR while exactly one acts as the local workspace sandbox — and the boring deploy-host failure mode that forces the discipline.
lfm/issues
self-host-stack4
Postiz is the heaviest thing we run
Postiz and its dependencies account for more than half the memory in the client projects that have it — and memory is 93% of the Railway bill. Nobody is visibly getting value back.
Normalize Paths Everywhere — one URL shape for every client + service
Today every tool lives at a raw Railway hostname; the goal is one owned, legible shape — lossless.at/<client>/<service>/… — for humans and agents alike.
Which domain hosts what — lossless.at vs didi.sh
Client-facing apps have landed on both domains by accident of chronology, not decision. Nothing is broken; the next deploy will guess, and guess differently than the last one.
self-host-stack/issues
corpora-builderai-labs3
Need an Elegant Resolution to Source Pointers vs. Master
One source, many folders, is the design. But for 75 sources the body sits in an untriaged inbox file the scoped read never reaches.
24 Orphaned bin/ Objects From a Half-Migration
A test that checked the object existed but never the pointer. Ghostscript's nondeterminism turned a sequencing mistake into 24 untraceable objects.
corpora-builder/issues
fullstack-vcastro-knots3
Troubleshooting SSG Authentication and the Port to SSR with a Database
Optimize for Localized OpenGraph Metadata and Banner Image with Overlay
We want WhatsApp / iMessage / Twitter shares of any project page to surface a banner image that's visibly *about that project* — title baked in, not just a generic site-wide image. Today we have project-specific title and description in the OG meta tags but a shared placeholder image. Documents the four paths to a fix and the trigger that should reopen this work.
fullstack-vc/issues
context-v-corpus3
Make Every Repo in the Tree OKF Compliant
61 context-v bundles, 1,083 docs, most now OKF compliant. What's done, what's left, and how to finish the rest.
Astro Knots Skills Live in Two Places, and Will Diverge
The skills that define how we build Astro sites are split between lossless-agent-skills and astro-knots, and astro-knots-mcp is about to copy them into every new site. One canonical home, and a corpus that ingests it once.
context-v-corpus/issues
lossless-monorepo3
Dependabot Alerts — Triage Playbook for Lossless Repos
The bulk-dismiss script with categorized rationales cleared 86 Dependabot alerts across three Obsidian plugins in about five minutes.
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.
lossless-monorepo/issues
flave-aiai-labs2
The lfm barrel imports node builtins, so it cannot be bundled for a browser
A consumer that only wants `parseMarkdown` still drags `node:crypto`, `node:fs` and `node:path` into the bundle, because the main entry re-exports OGCache. Same class of defect lfm already documented for plantuml — but in the front door.
flave-ai/issues