issues Search Results · language:Edge language:Python linked:pr language:C# language:JavaScript language:JavaScript
Filter by
5.1M results
Problem
README/AGENTS document one canonical flow: ingest raw sources → compile → verify later, with the marker taxonomy
(STALE/UNSOURCED/DRIFT) as the health surface. A real campaign ran the inverse ...
mattezell
Problem (field report — discussion-grade proposal)
The software-engineering template scaffolds team-engineering shapes: decisions/ components/ systems/ patterns/
incidents/ runbooks/ tech-debt (src/templates/software-engineering/template.js ...
Problem
orphans counts only [[wikilinks]] (src/verbs.js, the /\[\[([^\]|#]+)…\]\]/g matcher) — correct and by design. But pages
in the field wiki cross-reference in prose ( see bigfix-sync.md , Cross-refs ...
Problem (carried from field dogfooding, previously noted)
1. read accepts exactly one path shape — relative to wiki/ (src/verbs.js readPage()). Agents naturally pass
wiki/zone/page.md (repo-relative), ...
Problem
During distillation and human review, checking a page s citations means re-hunting every cite by hand — the field
campaign s agents ran sed -n X,Yp against authority files hundreds of times, ...
Problem
Two cheap invariants nothing checks, both proven failures in the field wiki:
1. Index header rot. wiki/index.md opens with _Last updated: 2026-06-03 | Total pages: 4 | Total sources: 0_ while ...
Problem
When an authority has ref set, plain tng-wiki ground still checks the working tree — the pin only applies under --at-ref
(src/ground.js: the refResolvable map is only populated if (atRef)). The ...
Problem
code_authorities[].path is resolved with resolve(wikiPath, a.path) (src/ground.js, checkGrounding()), so relative paths
are fully portable — but nothing expands ~, and init s prompt deliberately ...
Problem
The tool models trusted code (code_authorities) and in-repo sources (raw/), but the reverse-engineering / M A workflow
the README markets centers on a third thing it has no concept for: an external, ...
Problem
Two compounding gaps, surfaced by a 6-day / 22-page / ~30-commit grounding campaign (foglifter-notes-and-artifacts):
1. Churn detection is file-granular. The only signal that a cited authority ...
Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip! Restrict your search to the title by using the in:title qualifier.
Learn how you can use GitHub Issues to plan and track your work.
Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub IssuesProTip! Restrict your search to the title by using the in:title qualifier.