pip show exits non-zero for an absent package; under set -euo pipefail the
command substitution aborted build.sh before the self-heal could run — the
gate then failed the deploy with no message at all. Tolerate the missing
package (that is the case being healed) and report it.
The poller's private venv (.docs-publisher/.venv-docs) diverged from the
canonical one twice, each time silently delaying a deploy. Consolidate:
- poll-watcher.sh builds with the ONE canonical venv
(~/repos/docs/.venv-docs) while keeping its dedicated checkout (uncommitted
edits in a working clone must never block or leak into a deploy).
- New drift check: publishing/ + mkdocs.yml are compared with the canonical
checkout before every build; a mismatch fails the deploy loudly instead of
shipping logic the canonical source cannot reproduce.
- Pre-deploy gate: build.sh --check-only verifies the pinned toolchain and
every configured plugin (self-heals missing pins, fails loudly naming an
unpinned plugin).
- Alerting: 3 consecutive deploy failures -> marker file + ONE Matrix message
to the InferenceBot HQ room (hourly cap); counter resets on next success.
- The watcher re-execs itself when a deploy changed poll-watcher.sh, so the
running loop always matches the deployed one.
- webhook receiver (dormant) repointed at the canonical venv too; unit files
and README document the layout.
requirements.txt pinned only mkdocs-material, so a cold venv lacked mkdocs
and mkdocs-redirects — the exact gap that silently stalled the auto-deployer
today. build.sh now gates every build on the venv: it verifies the pinned
requirements (installing anything missing or off-version — fast local no-op
when current) and fails loudly if mkdocs.yml configures a plugin that
requirements.txt does not pin. --check-only runs the gates without building,
for use as the poller's pre-deploy check.
- greenpt/deepseek-v4.1-flash routes to GreenPT's base deepseek-v4.1-flash
id, not the deepseek-v4.1-flash-1017 snapshot (17 Oct 2026) that GreenPT
lists separately. Confirmed from the gateway registry mapping and
GreenPT's model card / model list, 2026-11-09.
- regolo/qwen-image serves Regolo's single Qwen-Image id, which Regolo's
catalog describes as the (2512) checkpoint — the December 2025 update,
not the newer Qwen Image 2.1 (2026-09-20). Regolo does not list 2.1.
- tinfoil/nomic-embed-text is now member-facing ($0.016/1M per Tinfoil's
catalog, TEE-protected, 768-dim, 8K ctx) — the model the co-op's own docs
search runs on inside the TEE.
- greenpt/green-embeddings added ($0.20/1M, 2560-dim measured, 32K ctx) — the
only genuinely distinct other embedding model in GreenPT's catalog.
- Embedding table now lists all three with pricing; quick-guide bullet updated.
- whisper-large-v3-turbo: $0.01 per request (flat, zero per-token) — the old
$0.05/1M-input row was stale (co-op/support#48)
- voxtral-tts: $0.002 per request (was 'listed $0 (verify on invoice)')
- new: tinfoil/voxtral-small-24b, Tinfoil's token-priced STT model
($0.20/1M in + $0.60/1M out), with the chunk-equivalent note for the
transcription route and a chat-with-input_audio example
- note why dashboard audio rows read '$0.01 · 0 tokens' (Tinfoil returns no
token usage for audio)
New gateway model (code/litellm 54925ca): /v1/embeddings, GreenPT-hosted,
4096-dim (measured through the gateway), $0.25/1M input from GreenPT's own
pricing, 32K input cap (provider catalog). Not a chat model — API-only like
the audio models, hidden from the chat picker. Also states plainly that
Tinfoil's nomic-embed-text is the operator-only docs-RAG embedding, since a
member read its absence from the model list as removal.
- condense the page to what a member needs: where services run (Infomaniak),
what backups mean to them, the .coop domain via domains.coop, mail via
Scaleway, the Matrix space and the accounts they may meet
- drop operator detail (migration narration, DNS record inventory, scheduled-task
internals, admin-only components, internal account/credential identifiers) to
co-op/ops-docs; fix a heading glitch where a line began with '#infrastructure'
- brand.css: light-mode .md-tabs uses the header's pale wash #e8f5e8 (was the
saturated --green-deep) with a warm hairline; dark scheme unchanged
Make clear this is the documentation, not the co-op homepage:
- site_name -> 'Inference Cooperative docs' (drives the <title> and the
header brand on every page)
- homepage h1 -> 'Inference Cooperative docs'
- footer gains a 'Co-op homepage' link to https://inference.coop/, added
in the existing copyright.html override alongside the Gitea source link
- mkdocs.yml: list 'Working with the agent' in the nav (a page not in the
nav is hard to find).
- working-with-the-agent.md: the operator token runbook moved out of the
published site into the git-only co-op/ops-docs, so the relative link
(operator-token-runbook.md) would 404; point it at the runbook's new home
in ops-docs, as infrastructure.md already does. Wording unchanged.
- The co-op now runs more than one isolated agent; the page covers all of
them and names infrastructure-bot.
- Disambiguates @inference-bot (automation account) from @inferencebot
(the steward agent members instruct).
- Names the mechanism behind "admitted members": a per-agent allowlist
plus mention-required rooms.
- Restates the deploy norm to match standing practice (bug and security
fixes deploy immediately and are reported; member-visible or risky
changes are confirmed first) and points a stricter norm at the forum.
- Off switch: who can actually reach it, and that stopping is not
restarting.
A first draft of the member-facing norms listed as a design goal on
co-op/support#17: where the agent speaks and listens, what to ask it for,
what not to ask it in a shared room, what it does without confirmation,
what always needs a human, and how it is stopped. Linked from the README
index and the Matrix section of getting-started. Nothing here changes how
the agent is configured.
brand.css and typography.css are referenced at fixed URLs via extra_css, so a
warm browser cache could keep serving the previous stylesheet after a deploy.
Add on_post_build to publishing/hooks.py: at build time copy each extra_css
file to <name>.<sha256-8>.css in the output and rewrite the <link> in the built
HTML. Any content change now yields a new URL. Sources keep their names; hashed
copies exist only in the build output and stale ones are pruned on rebuild.
The light scheme filled the header and tabs with green-deep, which read as heavy. They now
use the homepage's "open source" pill colour #e8f5e8 with ink text, and the deeper greens
are kept for accents -- links, active navigation and rules -- rather than as background
fills. The dark scheme is unchanged.
- README: render the Key links as real Markdown links (mailto: for the
contact address); drop the 'lives in a public git repository' note now
that the footer carries the source link.
- mkdocs.yml: add a theme override (custom_dir: overrides) that puts a
'Documentation source' link in the footer of every page.
- Move the operator runbook, maintenance notes and incident write-up out
of the published site into the git-only co-op/ops-docs repository;
remove them from the nav and repoint cross-references at Gitea.
The docs now have a dedicated Cloudron app (io.cloudron.surfer,
location docs.inference.coop, id 85b7ce06-e2af-49a4-bd4f-a9c2e692e3ab)
serving /app/data/public. deploy.sh writes there and nowhere else; the
two copies inside the marketing Surfer app (public-docs and
public/docs) have been deleted, so there is one canonical location.
SURFER_APP now defaults to docs.inference.coop and DOCS_DEST to
/app/data/public.
Light: warm neutrals (#e4e0d8 borders, #f4f2ec code, #6b7a62 muted) instead of
near-blacks; links use the dashboard's #4e7a4d (4.7:1 on cream).
Dark: replace Material's cold blue-grey slate (#1e2129 page) with the chat
overlay's deep-pine palette (#22271f page, #e8f5e8 text, #7ab87a accent), so a
dark screen reads as the co-op's green identity rather than stock Material.
Add .woodpecker.yml — install the pinned toolchain, run publishing/build.sh,
then publishing/deploy.sh. No build logic is duplicated; the publishing layer
stays the source of truth. Manual runs only for now: the push webhook is not
wired until the Woodpecker instance is restricted, connected to Gitea and
proven by a manual run.
At 360px wide the h1 was still 52px, because Material keeps a 20px root on mobile, so
"Cooperative" (297px at that size) left only ~30px of slack before breaking mid-word.
Headings now use clamp() to track the viewport and reach the same desktop sizes, with
word-break: normal, hyphens: none and text-wrap: balance so wrapping happens at the
space and the two lines are balanced rather than one word sitting alone.
Dark mode: the slate scheme set the header to #3f6b3e, a dark green on a dark page, so
the bar disappeared into the background. It is now green-mid with near-black text.
Typography moves to publishing/typography.css, loaded after brand.css, and declares
Figtree on the elements themselves -- Material defines --md-text-font-family on <body>,
so a :root value loses to it by DOM proximity. Heading colours are scoped to the light
scheme, since ink is unreadable on the dark one.
Material emits its own font variables and defines --md-text-font-family on <body>,
so brand.css's :root value lost to it by DOM proximity -- the same failure mode as the
palette, and the reason the site rendered entirely in the system font stack with
Material's default 32px/300 headings.
theme.font: false stops Material supplying typography, and brand.css now declares the
font on body, the navigation, the header and every heading, with heading sizes closer to
the website. Figtree is still self-hosted from publishing/fonts.
The theme was configured with primary: teal and accent: deep orange, so every page
shipped data-md-color-primary="teal" / data-md-color-accent="deep-orange" and Material
set --md-primary-fg-color and friends on <body>. Those variables then beat brand.css,
which sets them on <html>, because a value on the nearer ancestor wins for descendants
regardless of specificity. The result: cream background and ink from brand.css applied,
but the header, links and accents stayed Material's defaults.
primary/accent are now "custom", Material emits no palette of its own, and the co-op
variables in publishing/brand.css take effect.