From e3b9a90181acf23d09ab39a49d7a7a4733c2a922 Mon Sep 17 00:00:00 2001 From: Labyricorn Date: Tue, 11 Aug 2026 23:27:27 -0700 Subject: [PATCH] Document Labyricorn refresh dispatch --- .labyricorn/AGENTS.md | 16 +++++++++++++--- .labyricorn/README.md | 5 ++++- 2 files changed, 17 insertions(+), 4 deletions(-) diff --git a/.labyricorn/AGENTS.md b/.labyricorn/AGENTS.md index f82856f..86e8619 100644 --- a/.labyricorn/AGENTS.md +++ b/.labyricorn/AGENTS.md @@ -50,9 +50,19 @@ those directories. command example. - Do not claim that content is public merely because a push succeeded. Report push status and synchronization/publication status separately. -- When an authenticated refresh mechanism is implemented and documented, use - only its approved wrapper command and request at most one refresh for a pushed - commit. Until then, do not invent or bypass a trigger mechanism. +- After an explicitly authorized push that changes `.labyricorn/`, request at + most one refresh through the site repository's documented Gitea + `workflow_dispatch` endpoint. Use `POST` with `{"ref":"main"}` and an + `Authorization: token ...` header supplied from the approved + `LABYRICORN_REFRESH_TOKEN` environment or credential store. +- The endpoint is + `https://git.labyricorn.com/api/v1/repos/Labyricorn/labyricorn-site/actions/workflows/deploy.yml/dispatches`. + Never place its credential in the URL, this repository, an `AGENTS.md` file, + output, or logs. If the credential is unavailable, do not improvise: the + scheduled synchronization runs every 30 minutes. +- A successful dispatch only queues synchronization. Verify the Action result + and the imported revision on the public project page before reporting that + publication completed. ## Validation and handoff diff --git a/.labyricorn/README.md b/.labyricorn/README.md index e816593..fde40a5 100644 --- a/.labyricorn/README.md +++ b/.labyricorn/README.md @@ -34,4 +34,7 @@ Rules: The Labyricorn synchronization job reads content from an exact repository commit. Editing these records does not itself deploy the site; scheduled -synchronization is the publication fallback. +synchronization runs every 30 minutes and is the publication fallback. After an +authorized push, an assistant with an approved refresh credential may dispatch +the Labyricorn site's `deploy.yml` workflow once as documented in +`.labyricorn/AGENTS.md`; the credential must never be stored in this repository.