Skip to content

Refresh the public tree from the private repository (8 November 2026) - #25

Merged
RunTimeAdmin merged 1 commit into
mainfrom
refresh-2026-11-08
Nov 8, 2026
Merged

RunTimeAdmin merged 1 commit into
mainfrom
refresh-2026-11-08

Conversation

@RunTimeAdmin

Copy link
Copy Markdown
Owner

What

Brings the public tree up to the private repository's main as of 8 November 2026 (bb6be4c), 32 commits after the refresh of 6 November (8653006, #24). 147 files change (+26,061, -333): 47 new, 100 edited, none removed. One commit, with the account's noreply address as author and committer. Nothing else was changed on this side.

  • Gnosis, an eighth chain (chain id 100), behind its own switch, chain_gnosis. Its ERC-8004 identity pass runs once a day (migrations 0057 and 0058), reads names from the files the registrations link, and its ratings are counted. It has a chain page with a share card and lights on the home map, and the API takes gnosis as a chain. The claim flow for the owners of its agents is in, behind a switch of its own, claims_gnosis. The census of its registry is at /field/gnosis-registry-2026-11-06: the measurement, the queries, a typed data file and a test that holds the page to the data.
  • The Today block at the top of each registry census report: the counts of the report's first table as the directory stands now, beside the figures the report measured and the change between them. The dated report below it does not change. Base's block says why its counts fell.
  • Two public A2A registries as catalog sources, staged manual only, with their two approval records. The party rule between catalog sources: a registry run leaves out a party that another source's public record already holds. It had held only against direct A2A sources, because it read endpoint rows and a catalog record has none. Migration 0059 keeps the card host on the snapshot, so the rule holds between catalog sources too.
  • The Agenstry feed limits, raised, with a test on each of the four limits that drop records without a failure.
  • The footer and the mark. The home footer says who runs Nooscape, and the trademark mark is on the site once and in the README once, held by a test.
  • A fix in the lifecycle log. The running process is no longer listed as an earlier instance of itself.
  • The records for these, and to-do items 183 to 192.

How it was made

The same export script as #22 to #24: git archive of the private repository at bb6be4c, no history, the same scrub and the same build guards, which passed. No commit reached this repository's main since #24. The export differs from it by the private changes and the README, and by nothing else. The README's figures are the 8 November reading (62,759 listed, 302 reviewed), and its API section now lists gnosis.

Checked

  • Type check and build pass on a copy of this tree, and the suite passes there: 270 files and 4,975 tests passed, none failed. 801 tests were skipped on that machine: the ones that need a database, and a few that need Linux or OpenSSL. This pull request's gate runs them on a throwaway MySQL.
  • The repository's secret scan on the tree: nothing credential-shaped.
  • The 26,061 added lines were searched for addresses, hosting identifiers, emails, names, local paths and credential shapes: only test fixtures (documentation addresses, example emails, the local test database URL, and transaction and block hashes in the chain fixtures). A search of the whole tree for the identifiers scrubbed before finds 0 files, and a sweep of the whole tree for addresses and server names is the same as the last one apart from the new files.

To watch

  • The separate CodeQL check on the new code: the Today block (CensusToday.tsx, censusToday.ts), the A2A registry adapter and the Gnosis page and data file. Only gate is required. One alert is open on main from before (Refresh the public tree from the private repository (5 November 2026) #18, a tag strip in arcRegistryReport20261106.test.ts), and this change does not touch that file.

Merge with squash: a rebase merge writes the merger's primary email into the committer field.

🤖 Generated with Claude Code

Brings the public tree up to the private repository's main of 8 November 2026
(bb6be4c), 32 commits after the refresh of 6 November (private 8653006, #24).
Nothing else was changed on this side. It carries:

- Gnosis (chain id 100) as an eighth chain, behind its own switch: its
  ERC-8004 identity pass, run once a day, with names read from the files the
  registrations link and a count of its ratings (migrations 0057 and 0058);
  its chain page, share card and lights on the home map; the claim flow for
  the owners of its agents, behind a switch of its own; its registry census at
  /field/gnosis-registry-2026-11-06; and the API taking gnosis as a chain
- a Today block at the top of each registry census report: the counts of the
  report's first table as the directory stands now, beside the figures the
  report measured and the change between them, with the dated report below it
  unchanged
- two public A2A registries as catalog sources, staged manual only, and the
  rule that leaves out a party another source's reviewed record already holds
  now holding between catalog sources, with the host kept on the snapshot
  (migration 0059)
- higher limits on the Agenstry feed, with a test on each of the four that
  drop records without a failure
- a line in the home footer that says who runs Nooscape, and the trademark
  mark once on the site and once in the README
- the lifecycle log no longer lists the running process as an earlier
  instance of itself
- the records for these, and to-do items 183 to 192

The tree equals the export of private bb6be4c, apart from the scrub and the
withheld records (stubs). The README's figures are the 8 November 2026
reading, and its API section names gnosis.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@RunTimeAdmin
RunTimeAdmin merged commit d9ca888 into main Nov 8, 2026
4 checks passed
@RunTimeAdmin
RunTimeAdmin deleted the refresh-2026-11-08 branch November 8, 2026 17:33
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