#0055 is done: ThreadNet-Web be323ed checks in an .npmrc binding @sorb to rohana.
The bump that mattered was not the file but what upstream's .gitignore does with
it - it ignores /.npmrc, so the naive fix would have stayed local while CI kept
resolving against npmjs. Measured in an isolated tree: without the file pnpm goes
to npmjs and fails, with it the scope resolves to rohana at the integrity hash
the lockfile already carries, and with rohana unreachable the install fails
instead of falling back. threadnet-call only publishes and already sets the scope
in its own CI; gitops never touches it. ThreadNet-Web was the only consumer.
Four issues no longer describe reality, each verified rather than assumed:
- #0091 (gitops#61) was fixed when it was written - on_conflict: fail shipped in
ef04d86 and the MAS pod has run that config since 2026-08-11T14:08:41Z. Its one
deliberate remainder became #0043, which is closed and verified live.
- #0079 (gitops#46) asked for the Gitea migration and a central view. The
migration ran; the central view was decided the other way round - repo canonical,
GitLab mirrored (ADR-0012/0019) - which also answers the reachability trade-off
it left open, and better than its three options did.
- #0075 (gitops#40) is rejected, not done: it wanted new issues to appear in the
Gitea kanban automatically. Issues no longer live in Gitea and the board is
script-written. Nothing was accomplished; the question dissolved.
- #0098 is a rollout record whose only remainder, the macOS build, is #0022.
Three AARs move to harvested - every open item in them is tracked as an issue.
Checked and still accurate, so left alone: the wiki branch still exists on both
remotes (#0019), docs/TASKS.md and oldwiki/ are still there (#0085),
element-web-docs still names live resources (#0086), res/themes/element persists
(#0100), only WIKI_CANONIZE_TOKEN is set so TURN rotation still lacks its token
(#0084), gameserver still has zero push mirrors (#0032), the broken .6 package is
still published (#0101), and options.ts still builds simulcast layers regardless
of codec, which is what blocks VP9 (#0057).
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The mirror created the seven issues that had never reached the board
(management#33-39) and wrote each new iid back into its file. Without the
writeback the next run would create duplicates instead of recognising its own
work.
Group check after the run: the issue drift class is empty - 27 findings down to
20, 7 hints to 0, and not a single GitLab issue without a canonical file. What
remains is unrelated to the board: seventeen commit-hygiene findings parked in
#0053 and three component declarations.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
ThreadNet-Web resolves @sorb/threadnet-call-embedded from rohana only because
pnpm-lock.yaml pins the full tarball URL and CI installs frozen. There is no
.npmrc anywhere, so the moment someone bumps the version, pnpm reaches for
registry.npmjs.org instead. Hit while bumping to .8 for #0054.
Today that fails loudly with a 404 — but only because the name happens to be
unregistered on public npm. The protection is a coincidence, not a control:
register that name and the same command resolves successfully against a
stranger's package, in the one moment where a fresh download looks expected.
Documenting it is explicitly not the fix here; the checked-in .npmrc is, because
it removes the wrong path rather than warning about it.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Thore CimbalandClaude Opus 5