The workflow rules stop new empty pipelines; they do not remove pipeline 518, which
already exists and stays inside the check's eight-day window. Acknowledged until
2026-08-28 so the entry expires with the window rather than outliving it - if it is
still red afterwards, the fix was incomplete and the check says so again.
This is the case the mechanism was built for: known, dated, self-clearing, with the
root cause fixed rather than papered over.
The issue insists on measuring before building, so: the import was Element Web
1.12.17 in May, upstream is at v1.12.26, and GHSA-wrcp-5v3v-3j6v has been open since
2026-07-20 with "affected: < v1.12.22". We are inside that range. The other five
advisories concern 1.11.x and do not.
Severity is medium and the attack needs the client pointed at a malicious homeserver,
which our users have no reason to do. But the precondition is reachable:
disable_custom_urls is not set, so Element accepts an arbitrary homeserver by default,
and the desktop builds are handed out.
So the honest answer is overdue rather than urgent: a fork without a merge path took
four weeks to not close a known hole, which is exactly the latency this issue names as
the real problem.
One mitigation is available today and independent of the fork question - setting
disable_custom_urls removes the precondition for our users in one line. With
federation closed it is a reasonable setting on its own merits.
Running pruefe_prosa with a complete clone set resolved every SHA citation in the
repo except one, and that one is an Alertmanager silence id from 2026-08-15, sitting
in #0002 next to two siblings that were already listed as exceptions.
With it entered the repo reaches 0 errors and 0 unverified citations - every commit
named in documentation demonstrably exists in the repository it claims to be in.
sorb tested a group call after the restart and it works. That proves what curl could
not: the full OpenID token check through /_matrix/federation/v1/openid/userinfo still
completes with federation closed, so the whitelist genuinely does not reach that
endpoint.
It is also where option C finally died. Blocking /_matrix/federation at the edge would
have removed exactly this path, and nothing before the call would have shown it.
sorb chose C, fully disabling federation at the edge. Building it showed that would
have killed group calls: lk-jwt-service verifies OpenID tokens through
/_matrix/federation/v1/openid/userinfo and reaches it over the public name, so a path
block on /_matrix/federation is the mrtc outage again with a different cause. C was
dropped and B implemented.
The ADR records the measurement the decision rests on - zero destinations, zero remote
users, zero rooms with outside participation in four months - and the trap, so nobody
completes C later as a quick follow-up. Doing that safely means binding the auth
service to Synapse in-cluster first, which is its own undertaking with a call
acceptance.
Also recorded because it nearly slipped through: Flux applied the ConfigMap while
Synapse kept running its old config from 2026-08-01. The config is rendered at pod
start, so the change was inert until a restart - the same class as #0044. Verified
afterwards inside the running process rather than in the ConfigMap, with the client
API and the OpenID endpoint still answering.
The question sat open since July because nobody knew what closing would cost. It is
now measured: zero. No destinations, no remote users, no rooms with outside
participation, across four months of operation - while the federation API answers
HTTP 200 from the public internet, since the well-known delegation routes federation
over 443 and port 8448 being shut changes nothing.
So the trade is not reach against safety but an unused capability against Synapse's
largest remote-facing surface. Recommended B, an empty federation_domain_whitelist:
one line, versioned, reversible in minutes, and honest about what it does not do -
the endpoints keep answering, so the server becomes unengaged rather than invisible.
Decision remains sorb's.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Rolled out to matrix, authentik and monitoring, verified in two namespaces rather
than assumed: DNS resolves, federation still reaches matrix.org, the metadata service
is blocked, and the private path to 10.0.0.3 is intact with Alloy reporting no errors.
The issue stays open on purpose. Its actual demand - default deny with explicit
allows - is not met; egress is still open everywhere except link-local. Federation
makes that unwritable as a list while it stays open (#0060). What is now on record is
the inventory that makes the next decision possible: monitoring and authentik have a
nameable set of destinations and could take default deny, matrix cannot.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Before anything else: NetworkPolicy really is enforced here. k3s runs flannel and the
policy controller inside its own process, so the absence of pods in kube-system
proves nothing - measured instead, with a counter-probe. synapse-main reaches
matrix's postgres and authentik-server does not, exactly as allow-ingress-postgres
says. So the existing ingress rules are real protection and egress rules will bite.
The textbook first step - allow 0.0.0.0/0 but except RFC1918 and the metadata
service - would have cut two things here, both over 10.0.0.3, CFGMON on the private
Hetzner network. Alloy remote-writes metrics and logs there, so monitoring would have
gone silent, and nothing reports the failure of the reporting path. And the TURN
rotation reaches Gitea through a hostAlias to that address because the public route
was unreliable, so the rotation push would have died a day after we got it working
again.
That also settles #0008 harder than the absence of a firewall rule could: the cluster
reaches Prometheus and Loki privately, so 9090 and 3100 are demonstrably not needed
publicly.
Proposed step 2 is therefore narrower and nearly risk-free: block only the metadata
service, 169.254.0.0/16, while leaving federation, ACME, SMTP, registries and the
private path open. Nobody here needs the metadata service, and the hard part of this
issue - federation to arbitrary servers - is not touched at all.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
"Alert delivery is disconnected" was true when the issue was filed and untrue by
that evening. I carried it as a production blocker on the strength of the issue text
alone, which was wrong: the rules aggregate per target, save_state runs inside the
loop including the failure branch, the security null route is gone, and coturn is
pinned. All of it verified in the code, not inferred.
What genuinely remained were the two smaller review points, and both are done now.
The exporter no longer erases first-seen timestamps when a report fails to parse -
pruning is limited to targets actually read this round, proven in both directions.
And because TrivyScanStale cannot by construction report a target that never
produced a report, the exporter now emits trivy_reports_total and
trivy_report_read_errors with an alert on each.
Priority corrected from high to medium to match what was actually open.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
sorb created the project access token with exactly what the job needs: Maintainer,
because main is protected with push=Maintainers, and write_repository only, because
the job pushes and never calls the API. Checked through the API without touching the
value.
Proven rather than assumed: a throwaway job pushed a ref with that token and removed
it again, leaving main untouched and no branch behind. So the value reaches the job -
protected variable on a protected branch - and it may write. The first real test is
the rotation on 2026-09-01.
Recorded as a future silent failure: the token expires 2027-08-19, and because the
job runs green while idle, nobody would notice until the next real rotation after
that date. Exactly the #0104 class, so it belongs in a calendar rather than in hope.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Decision sorb. Both questions are answered: there is no rule for 9090 or 3100 on
CFGMON and Hetzner denies inbound by default, so Weg A never had anything to
restrict; and the state now has ports-soll.md plus pruefe-ports.sh holding it.
The reservation is written down rather than glossed over: from sorb's network the
must-be-shut half cannot be proven, because the site coupling grants privileged
access there. The script says so instead of reporting false green, and an external
run - judged excessive for routine use - is named for the case that warrants it.
Whether the GAME push survives the vSwitch move belongs to #0002.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Measured from the cluster the port is shut; measured from sorb's Mac it answered,
because the lab reaches CFGMON over the site coupling, which the cloud firewall does
not filter. The rule is fine and so is the service.
What was actually broken is my check: its counter-probe proves the method works, not
that the vantage point is external. pruefe-ports.sh now probes its own location
first and refuses to score the closed-port half from a privileged network.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The CFGMON firewall has no rule for 9090 or 3100 at all. Hetzner denies inbound by
default, so the ports were never closed - they were never opened. That matches the
2026-08-01 observation exactly and makes Weg A moot for the public path.
While measuring the ports the rules do permit, port 53 answered from a public
address and resolved google.com recursively. The visible rule names only
10.58.73.17 as its source. Recorded here as a separate finding rather than decided
inside this issue.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Three corrections to questions I should not have asked again.
#0103 is implemented: autoEnrollGroups points at wiki-anwender, verified in the live
database rather than from the job log. The decision was already in #0049 - the role
model was built, only the way in was missing.
#0102's blocker was in the documentation all along: maintenance-notify sends under
.de, not .chat, via IONOS on 587. The MAIL_FROM in config.example is an example, not
the operating state. So hardening .chat cannot break maintenance mail, and Authentik
remains its only .chat sender - DKIM-covered.
#0008 is not resolved by the console screenshots: they show fw-matrix-cx42, the
Matrix host, while the issue asks which rule keeps 9090 and 3100 shut on CFGMON.
Still open. What they did show is worth keeping: SSH and the Kubernetes API are
properly source-restricted, and several rules open ports to everyone where nothing
listens - including an inbound smtp 587 that cannot help the outbound sending it was
presumably added for.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The 2026-08-15 recheck found the ports closed but nobody had decided that and
nothing recorded it, so the next firewall change could have reopened them unseen.
notfallhandbuch:pruefe-ports.sh plus ports-soll.md close that half, measured rather
than derived, and check both directions - a reachability-only check would never
notice telemetry standing open.
Still needs sorb: the shared look at the Hetzner console. The script says what is
reachable from outside; which rules produce that, and whether they stand there on
purpose, only the console says.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Agreed with sorb. Two additions, both inside the project section - sections 1-5 are
the neckbeard baseline and stay byte-identical, which is also why the repo map's
scripts row was left alone rather than corrected in place.
"The red pipeline IS the alarm" now carries what it silently assumed: that green is
the normal state. The counter-example is named with its date, because the abstract
rule did not stop this from happening - the job stood red for nine days and that is
precisely why nobody looked.
A Prüfungen section lists the eight scripts the repo actually has against the two
the frozen map names, says when each runs, and states the acknowledgement rule:
known findings are acknowledged, not tolerated, every entry carries an expiry,
"permanent" is only expressible as an ADR reference, and leaving a check red is a
finding in itself rather than a neutral state.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Found while auditing whether everything is documented per the framework. The
automated checks were all green, which is the point: they check artifacts against
the schema, not prose against reality.
The README's structure table named four directories that do not exist - decisions/,
vision/, hosts/, shared/ - and sent readers to axionwiki.lab, which answers 404 and
was retired by ADR-0014, citing the superseded ADR-0006 as if current. AGENTS.md
says plainly that wiki.lab is gone and not to look for it; the repo's own entry
document said the opposite. Replaced with the layout that is actually there, plus
the checks and where acknowledgements live.
roadmap.md carried the same two staleness: "Docusaurus läuft" with an end-of-August
deadline for a question ADR-0014 already answered, and the board build-out from
gitops#46, which was decided the other way round and closed today. Both marked done
with what was actually decided, since a roadmap that claims open work is finished is
worse than one that is merely behind.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The framework audit found this missing. Acknowledging known findings is a process
decision about how the alarm system treats exceptions, and AGENTS.md is explicit
that documenting an exception instead of deciding it is itself the error. It lived
only inside #0104 and #0105, which are issues, not decision records.
The ADR carries the reasoning the issues could not: why option C beat working the
backlog down first or tolerating red, and why the obvious objection - an exception
list is a candidate for the next blind spot - is answered by the three rules rather
than waved away. It also records what is deliberately not acknowledged, the
transient mirror divergence, because that message is the only signal if a mirror
truly stops.
One consequence is stated plainly rather than discovered later: acknowledgements
bind to substrings of the finding text, so fixing or moving a cause can change the
wording and require the entry to follow. Stable finding IDs would avoid that and
would make the file unreadable without special knowledge; the trade is taken
knowingly.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The first CI run after the acknowledgement list went in was still red, so the
"all three green" line in #0104 was premature and is corrected rather than left
standing.
Two things it showed. Disabling the wiki mirror changed the finding's wording from
"Mirror wiki: counterpart unreadable" to "wiki: no active push mirror", and since
acknowledgements match on substrings, the entry no longer applied. Added. That is
the cost of a list readable without special knowledge: fix or move a cause and the
acknowledgement has to follow, otherwise it goes red - correctly.
The second finding, management mirror divergence, is deliberately NOT acknowledged.
It appears on any run starting minutes after a push because the mirror lags, and
acknowledging it is tempting - but that same message is the only signal if a mirror
ever really stops (#0028). It stays sharp; a run right after a push is briefly red.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Decision sorb. The mirror from axion1337.chat/wiki to sorb/wiki is off. It pointed
the wrong way: per ADR-0015 Wiki.js writes to sorb/wiki from the cluster and
canonize_wiki pulls it back to git.lab, so this mirror would have overwritten the
wiki content with git.lab's state. It had never run once - status none, no error -
which was luck rather than design.
Whether the wiki project stays at all is deliberately not decided now. sorb wants
that conversation immediately before project completion, once production readiness
is reached on everything else, so #0105 carries it as waiting with that as its
stated reason rather than as an open task somebody might pick up.
The group check's finding is acknowledged until 2026-12-31 rather than permanently.
A permanent acknowledgement would need an ADR, and writing that ADR is exactly the
decision being postponed; a date instead means that if the project outlives it, the
question asks itself again.
Both scheduled checks now reach zero open findings.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The group check carried 17 commit-hygiene findings that sorb deliberately deferred
to the history pass, plus two known items. Acknowledged until 2026-11-30, which
takes the check from 20 open findings to one.
Each commit is acknowledged by its own SHA rather than by a pattern. A rule like
": Echtzeit-Stempel" would have been one line instead of seventeen and would have
swallowed every future violation with it - the blind spot this whole mechanism
exists to avoid. As a side effect the entries clean themselves up: once the history
is rewritten they match nothing and report themselves for removal.
What remains open in both checks is the same single real finding, and it is new:
the GitLab project "wiki" is undeclared, and its push mirror to sorb/wiki has never
run once - status none, no error, no successful update. Per ADR-0015 that direction
is wrong: Wiki.js writes to sorb/wiki from the cluster and canonize_wiki pulls it
back to git.lab. Had this mirror ever fired it would have overwritten the wiki
content with git.lab's state. It stays red on purpose, because it needs a decision.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
All three scheduled checks were permanently red, which is how a nine-day outage of
the canonize job went unnoticed: one more red cross among red crosses is invisible.
A check that can only ever be red cannot report anything.
An acknowledgement takes a known finding out of the red verdict without hiding it -
it still prints, with its reason and its deadline. Red is reserved for what is not
acknowledged, which is to say: for the new.
Three rules keep the list from becoming the next blind spot, which is the obvious
objection to this whole idea:
- Every entry needs a deadline. Once it passes, the entry stops acknowledging and
says so, so the finding counts again.
- "Permanent" is only expressible as an ADR reference. A permanent exception
without a decision record is already an error per AGENTS.md; here it cannot even
be written down.
- An entry that matches nothing reports itself, so the file cannot quietly
accumulate lines for problems that no longer exist.
Four entries to start: notfallhandbuch (ADR-0016, deliberately unmirrored),
threadnet-wiki (ADR-0015, the wiki mirrors the other way round), gameserver (sorb:
not part of ThreadNet - dated, so the ADR-or-move decision does not drift), and the
zero-job pipeline artifact.
Verified rather than argued, including the counter-proofs #0104 asks for: today
four are acknowledged and one real finding stays red; adding a fresh finding still
turns it red; and with the clock moved past the deadlines the dated entries stop
acknowledging and report themselves. The scope column was added after the first run
showed each check reporting the other's entries as ineffective.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Decision sorb. AGENTS.md makes a red pipeline the alarm, with no second channel by
design. That only works while green is the normal state, and right now none of the
three scheduled checks reach it: canonize_rotation was red for nine days,
gruppenpruefung is red daily on 20 findings of which 17 are deliberately deferred,
and stillstandspruefung aborts daily for a missing GITEA_TOKEN. The management
pipeline has failed every day since at least 2026-08-12.
canonize_rotation is the proof rather than the anecdote: it failed for nine days on
a conflict touching both TURN secrets and the client image tag, and nobody noticed,
because one more red cross among red crosses is invisible. It surfaced only because
someone looked for an unrelated reason.
The issue asks how "known and deferred" gets distinguished from "new" without the
deferred work blocking the channel, and recommends acknowledging #0053's findings
with an expiry date while fixing #0031 outright. Acceptance requires showing a
freshly introduced finding still turns the pipeline red - demonstrated, not assumed.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Decision sorb. mas-cli locked the account and killed one OAuth and two browser
sessions, so signing in is no longer possible. deactivated_at stays empty though:
lucky now sits where scanner-test sits, not where @bojeledoggo does.
This MAS version's CLI has no deactivate-user - only lock/unlock. Full deactivation
runs through the admin API or Element Admin and therefore through an admin token,
which does not belong in a session. Locking takes the effect forward until sorb
makes it final with a click.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Decision sorb. The account had no name, no email, no group, one login on the day
it was created in May and nothing since. The delete removed exactly one row with no
dependent objects, because nothing was ever attached to it.
sorb's caveat was right but did not apply here: Matrix accounts cannot truly be
deleted - Synapse only deactivates, and the localpart stays reserved so nobody
inherits a former identity's history and mentions. That is why @bojeledoggo is
deactivated rather than gone, and that is the end state rather than a half measure.
Boje was never a Matrix account: no row in Synapse, none in MAS, no link. The
limitation governs the other account, not this one.
Two of the checklist's four lines are now done. The test rooms and clark/lucky
remain; both accounts are still active in Synapse.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Checking whether Boje is deactivated in Synapse produced the answer to three of
this checklist's four lines. @bojeledoggo is deactivated, so that item is done.
clark and lucky are still active, so that one is not.
Boje is the odd one: the account exists only in Authentik, created 2026-05-15 with
a single login that same day and nothing since, no email and no group. There is no
@boje or @Boje in Synapse and no upstream link in MAS, so the identity never
completed a Matrix login. The open question is less "add the email" than "does this
identity still belong anywhere".
Recorded because the name similarity has misled once already: @bojeledoggo,
Boje and elbojoloco are three different accounts.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Decision sorb. elbojoloco joins apo in wiki-anwender, so both read /anwender and
the start page while betrieb/* stays closed. Recorded because the addendum's table
would otherwise still list the account as having no effect.
The grant takes hold at the next login - the groups claim is minted during sign-in,
not continuously - and elbojoloco has never signed in to the wiki, so the account
gets created and mapped on first attempt.
Boje is still undecided, and clark and lucky remain test accounts slated for
deletion in #0074. The silent dead end persists for them, which is why the grants
do not close this issue.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
apo reads the wiki now. Checking every other configured user turned up the bigger
finding: Authentik has a group wiki-zugang with four members, and Wiki.js does not
honour it. Groups map by name, and the wiki only knows wiki-anwender and authentik
Admins - so elbojoloco, clark and Boje hold membership that does nothing, while the
name promises the opposite. Nobody noticed because none of them ever attempted a
login; Wiki.js has exactly two OIDC users.
The reason is a leftover: two Authentik applications share the display name
"ThreadNet Wiki". The one carrying the wiki-zugang policy has no provider at all -
an empty shell from the Docusaurus forward-auth era that ADR-0014 retired. The live
wiki-js application carries no policy binding, so it is open to any authenticated
user and the whole separation rests on a group assignment nobody looks for there.
So the trap cuts both ways: granting wiki-zugang grants nothing, and the real
application is ungated at its own layer. Acceptance now also covers retiring the
dead shell, resolving wiki-zugang, and the two empty leftover groups.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Decision sorb, after diagnosing why @apo could not reach the wiki. apo logs in
fine; the account exists since 2026-08-16 and was used again today. It is in no
group, and wiki-anwender has zero members, so the wiki is effectively admin-only
and every non-admin who ever tried met the same wall.
Three deliberate settings compose into a dead end: OIDC self-registration creates
the account, autoEnrollGroups is empty so it gets no group, and Guests was stripped
to no permissions while the only rule for home belongs to wiki-anwender. Default
deny then applies to every path including the start page - the user sees nothing
rather than a reason, and at the current log level nothing records the attempt
either. Same class as the mrtc outage: healthy, green, unusable, silent.
The issue asks for a decision rather than assuming one: auto-enroll into
wiki-anwender (the population is already curated by the invitation token, and
betrieb/* stays admin-only through default deny), or keep per-person curation and
make the dead end speak. Acceptance is a real login, not a config diff.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Decision sorb. ADR-0002 held that all project issues live on git.lab. Since
ADR-0012 and now ADR-0019 the canonical place is docs/issues/ in this repo, with
GitLab as the generated mirror - so that sentence stood in the record as a valid
rule next to its own opposite.
Only that sentence falls. ADR-0002 also moved the backlog repo into the lab and
named the lab the source of truth; git.lab stays canonical for code (ADR-0001) and
the repo stays where ADR-0002 put it. Because a bare "superseded" would read as if
the move were undone too, ADR-0019 now carries a section drawing the line, and the
superseded_by pointer leads a reader there. ADR-0002's body is untouched, matching
how ADR-0006 and ADR-0007 were retired.
ADR-0005 is deliberately left accepted: the WIP limit, the status labels and the
rule that only sorb promises work all still hold - only "the board is the truth"
moved, and ADR-0012 already records that.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Steps 2 and 4 were done today with the first mirror run and the milestone on
gitops#61. Step 3 turned out to need nothing: gruppenpruefung carries the same
schedule rule as stillstandspruefung, and the single daily schedule therefore runs
both. Verified on pipeline 472 rather than inferred - both jobs ran, both ended
red, which is the alarm doing its job.
What that leaves is a naming trap worth stating: the schedule is called
"Stillstandsprüfung (täglich)", so nobody looking for the group check finds it
there, and disabling the schedule for one reason silently disables the other check
too. Renaming is a click and belongs to sorb.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
#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>
Decision sorb: the mail hardening carried over from the mrtc diagnosis becomes an
issue. Writing it up corrected the premise the AAR and dns-soll.md carried:
#0006 hardened axion1337.DE, the zone with the real mailboxes, and it stands at
p=reject. The platform zone .chat was never its subject and still resolves its
_dmarc as a CNAME into IONOS' shared p=none - so the policy for our own domain is
set by IONOS, and RFC 7489 passes that none down to all seven service names.
Two senders are documented rather than assumed: Authentik as gamemaster@ via
IONOS SMTP (DKIM-covered), and maintenance-notify as wartung@ over an msmtp
config whose provider the template leaves open. That second path is why the issue
puts "clarify the senders" ahead of any policy change - p=reject before that
question is answered breaks maintenance mail silently.
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>
ADR-0012 made docs/issues/ canonical for the management scope only and left
gitops, ThreadNet-Web and threadnet-call on GitLab "until the component adopts".
That split produced exactly what it invited: two numbering worlds where
management#20 and gitops#20 are different issues, drift nobody had to answer for
(gitops#61 carried no milestone since 2026-08-11), and component backlogs that
host sessions without lab access cannot read at all.
The 46 open component issues are now files 0056-0101. The file id is the
group-wide identifier; provenance lives in the frontmatter (new field `projekt`
plus gitlab_iid) and in the filename, so "gitops#61" still finds 0091. Bodies are
copied verbatim; comments and history stay on GitLab, as with the 2026-08-11
management import.
Both scripts learned the second dimension: spiegel_issues.py routes each file to
its origin project, reopens issues that are open in the repo but closed on the
board, and writes the new iid back after creating one; gruppenpruefung.py checks
drift across all four trackers instead of management alone. What the mirror
cannot decide stays a finding, not a silent state.
Two things needed a hand, both recorded in the files: gitops#61 had no milestone
(M1 - it is a live account-takeover path) and carried two area labels where the
schema holds one. The Gitea migration footers in the imported bodies point at
decommissioned trackers; their links are removed, the provenance sentence stays.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The five-day group-call outage from the deleted mrtc A record had no management
record at all - the fix, the diagnosis path, and the lesson lived only in the
session. The AAR records why nothing alarmed (DNS-01 certs and pods stay green
without an A record), the exact dating via token-vs-join counts, and the
countermeasure that already shipped (notfallhandbuch dns-soll.md + pruefe-dns.sh).
gruppenpruefung's nine real-timestamp findings join #0053's history pass -
same class, same decision, recorded so the next session repairs nothing
unilaterally.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Opt-in plus the feature gate make a mobile failure consequence-free: it only
affects a user who switched the filter on, and their way out is the checkbox.
Nothing about this effort remains open.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Decision sorb: the filter is live in v0.5.4, proven in real calls on both
engine families, gated for rollback, and regression-tested on all three silent
failures found along the way. The phone test stays deliberately deferred; if it
becomes necessary it is a new issue, not a reopen.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
LiveKit's setProcessor swaps the sender track behind an optional chain; when
Safari's timing leaves the sender unset at that instant, the swap is skipped
silently and the raw microphone stays on the wire. The fork now verifies and
enforces the swap. Also records two instructive diagnostic dead ends: a sine
tone is noise to a speech model, and two devices in one room invalidate any
listening test.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Records the decision (per-track AudioContext instead of webAudioMix), the
implementation state (v0.5.2, defaults never carry a processor key, dev-only
opt-in via two localStorage keys), the discoverability stumble from the first
test attempt, and the two-stage acceptance that gates opening the feature.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The first production image carrying the filter broke unmuting for everyone.
Records both causes (missing AudioContext on the on-path, a stray
processor: undefined leaking into getUserMedia constraints on the off-path),
the fix with its deliberately-red-first regression tests, the passed two-person
acceptance call, and the standing lesson: for changes in the microphone path,
a real-call acceptance is a rollout precondition, not an afterthought.
The filter stays gated off until the webAudioMix decision - that follow-up is
what makes ADR-0018 implementable or refutes it.
Co-Authored-By: Claude Opus 4.8 <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>
Rolling out revealed that the first implementation would not have worked in
production: Element Call ships only as the embedded npm package, and that build
sets publicDir: false because upstream's public/ holds nothing but a favicon.
With that value everything builds, standalone works, and the filter is dead only
inside the widget — verified, not assumed.
Fixed in threadnet-call d270e0c and confirmed end to end: the widget URL resolves
to the model path and the CI artifact carries the assets, not just the local build.
Also corrects a number I gave when asking for the asset decision: the package goes
from 41 to 66 MB, not from 2 to 25 — it already contained source maps and the
crypto and vision wasm.
publish_npm stays manual by design and is sorb's to trigger.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
All repo checks green including the connection factory tests that cover the
changed noiseSuppression logic. Two findings while building improved the numbers:
the Dockerfile's gzip glob missed the model wasm in its subdirectory, costing
15.7 MB instead of 4.1 MB per client, and the 23 MB verifiably stay out of the JS
bundle, so the opt-in lazy load works as designed.
sorb chose to commit the assets rather than fetch them at build time — fetching
would have reintroduced the very third-party dependency we removed at runtime,
just moved to build time.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
sorb's decision after the prototype: integrate DeepFilterNet3 as a LiveKit track
processor, off by default, assets fetched only when the user enables it, checkbox
plus slider, 35 percent default.
Opt-in is what makes the 23.3 MB affordable — only those who benefit pay for it.
Three of the source specification's assumptions did not survive measurement and are
recorded as rejected alternatives: the dry/wet mixer (the model limits attenuation
natively, and mixing raw signal back would return the keystrokes), the Rust/wasm
build (a maintained package makes it unnecessary), and loading assets from the
vendor CDN (every participant's IP to a third party at call start).
Mobile stays untested by choice; since the filter is opt-in it simply stays off on
weak devices, so that is a follow-up rather than a blocker.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Built the throwaway prototype and sorb tested it: keyboard gone, voice natural,
at 35 percent rather than the 100 percent the spec assumed as default. That
settles the control question — the package exposes setSuppressionLevel and the
wasm carries atten_lim, so DeepFilterNet limits attenuation natively and the
spec's dry/wet mix drops out entirely, taking its missing delay node and phase
problem with it.
Measured what the spec had guessed: 23.27 MB per client, an order of magnitude
above RNNoise. Also found that the package fetches model and wasm from a
third-party CDN at call time, which a self-hosted platform cannot accept — the
asset URL is configurable and the prototype already serves them locally, so that
path is proven rather than assumed.
Still open and decision-relevant: CPU figures, the phone, and the standing cost of
carrying this through every upstream rebase.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
