Skip to content

Link census: navigation sites as a fourth token kind, listed per repository - #187

Merged
trick77 merged 3 commits into
masterfrom
feat/link-census
Sep 17, 2026
Merged

trick77 merged 3 commits into
masterfrom
feat/link-census

Conversation

@trick77

@trick77 trick77 commented Sep 17, 2026

Copy link
Copy Markdown
Owner

"In claims-ui, what links lead to apps outside it?" is a listing, and search returns twenty chunks about a mechanism. Nothing in the index recorded where a UI navigates to, and no path enumerated anything per repository.

  • edges.KindLink: every navigation site (href=, [href]=, routerLink, <Link to=, window.open(, window.location.href =, .navigate() in markup and script files, with the text at the site as its value. A UI seldom writes the host as one literal (${environment.portalUrl}/claims), so the site is what can be extracted; the symbol walk resolves the variable from the landing. Markup gets the link branch only, never the route rules. Skips useLocation, data-href, xlink:href, sprites, stylesheets, asset paths; reads JSX braces.
  • Links never cross: NeighboursWith/Holders refuse the kind. Flow corpus unchanged, 27/30 product and 28/30 reranked.
  • Understanding.Census, persisted on Scope: with a named repository the pipeline seeds the gather with the sites (40 files, a third of the budget, never evicted) and hands the prompt the full listing as an index block, one line per target with its places. No repository named, no census. Resume and re-explain rebuild the listing.
  • Trace: "+40 of 57 link sites" beside the boundary chip.
  • Migration 0027 forces a re-index, as 0015 did, or settled repositories never get the tokens.

Real-data check on the Sock Shop front-end: 221 sites over 45 targets, no junk class beyond jQuery template fragments. Not checked against a real Angular/React repository yet.

…sitory

A UI question like "what links lead to apps outside this repository" is a
listing, and search returns twenty chunks about a mechanism. The indexer now
records every navigation site (href, routerLink, window.open, location
assignment, router.navigate) in markup and script files as a link token,
with the text at the site as its value: a UI seldom writes the host it links
to as one literal, so the site is what can be extracted, and the symbol walk
resolves the variable from the landing.

Links never cross: two UIs pointing at one portal are not linked, and the
flow corpus stays at 27/30 and 28/30. The understanding step reads a census
field; with a named repository the pipeline seeds the gather with the sites
(cap 40, one per file) and hands the prompt the full listing as an index
block. Forced re-index, as 0015 did, so settled repositories get the tokens.
…ap landings by budget

A bare "location =" is React's useLocation() in every routed component,
so only window.location, document.location and location.href are sites;
data-href is not href; a stylesheet tag anywhere on the line and link.href
in script are skipped. JSX to={"/x"}, to={to} and to={{...}} are read
through the braces.

Landings now stop at a third of the gather budget as well as at forty
files: seeded whole and never evicted, forty full chunks would leave the
walk nothing, and the environment file the sites name is the point. The
prompt no longer calls a listing cut at 200 complete, a landing is no
longer counted as a reference in the trace, and a re-explain rebuilds the
listing like the structure block.
…arget

xlink:href, <use href> and a relative href to an .svg/.png/.pdf are files,
not places; an absolute URL to a document stays. The listing groups the
sites by target with up to three places each: the Sock Shop front-end has
221 sites over 45 targets and named index.html fourteen times.
@trick77
trick77 merged commit 05c8f09 into master Sep 17, 2026
2 checks passed
@trick77
trick77 deleted the feat/link-census branch September 17, 2026 17:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant