Code changes, week of 2026-11-02 – 2026-11-08 · 37 commits

What it is

Code activity

Where HEY read it

GitHub · Commits that week ↗ · Repository ↗

When it happened

In the week of Mon 2026-11-02 – Sun 2026-11-08 (UTC), dated by the source to the week

HEY first saw it

2026-11-02 (11d ago)These are two different clocks: when the work happened, as the source dates it, and when HEY first read it. A week of code activity is one record, which HEY writes when it first sees the week and keeps up to date while the week runs, so HEY can first see it before the week ends.

What changed that week

37 commits that week, not counting automation or merges.

• verification inputs for the third endowment set 2026-11-02
• share cards for every console page: a 1200x630 card per page in the site's design, rendered from one list by pnpm og, with its own title,… 2026-11-02
• publish the sources of the selling router and the first endowment factory, marks and deployer: exact matches, built from the commits they… 2026-11-02

How it is backed

Source-backed

Counts toward building

Counted once with its code week: ship:47eb8f45-a8c0-4ddc-a422-c47f6ca25492 stands for it in activity status and Build Momentum.

Records behind it

• Github repo, read 2026-11-02 ↗

What it does not say

A ship says what was shipped and where HEY read it. It is not a judgement of quality, of the team, or of what the token will do.