From bd19da9959ffa221f0cdb5dabb6b3ad60f19d06e Mon Sep 17 00:00:00 2001 From: Bendik Aagaard Lynghaug Date: Tue, 25 Aug 2026 15:38:08 +0200 Subject: [PATCH] Pin portal v0.2.3 - attended-bucket lint, first-nav fix; document the rule Co-Authored-By: Claude Fable 5 --- .gitea/workflows/deploy.yml | 2 +- README.md | 7 +++++++ 2 files changed, 8 insertions(+), 1 deletion(-) diff --git a/.gitea/workflows/deploy.yml b/.gitea/workflows/deploy.yml index 5228bf3..a44b443 100644 --- a/.gitea/workflows/deploy.yml +++ b/.gitea/workflows/deploy.yml @@ -18,7 +18,7 @@ on: - .gitea/workflows/deploy.yml env: - PORTAL_RELEASE: v0.2.2 + PORTAL_RELEASE: v0.2.3 INSTANCE: uhhm-portal jobs: diff --git a/README.md b/README.md index ceecd15..df28dac 100644 --- a/README.md +++ b/README.md @@ -212,6 +212,13 @@ review resource's transitions — fireable by whoever holds one specific record's `?chain=` link plus its matching email (the unsubscribe pattern). +**Attended buckets** (lint-enforced): every `record_as` bucket must be +read by some `kv` resource in this repo (a desk or listing) — or its +`aggregates.yaml` entry must carry `attended_by: ` naming the automation that does. A bucket nothing reads fails +lint, so no publicly collected answer can land where no one will ever +see it. + ## Routing: the tree is the router The `questions/` directory tree is the URL tree — `index.yaml` names