sam 5f9eda24f5 fix(gitea): honour each call's context, SDK branch linking, real 404s, paginated labels
Every call shared one SDK client whose context was background, so no caller
could cancel a Gitea request; each call now binds its own. LinkBranch
hand-built JSON over raw HTTP and posted to an endpoint Gitea does not have;
it sets the issue's ref through the SDK. PRState and VerifyPush matched error
text instead of the status, label lookup stopped at the first 100 labels,
merges ignored the repository's merge style, and a review of the token's own
pull request requested changes Gitea refuses.
2026-10-25 18:11:39 +11:00

archipelago

The archie-core marketplace. One directory per extension surface; each surface directory holds one subdirectory per extension.

secret-engines/<name>/   package.yaml + Go source, served over secretengine.v1
skills/<name>/           package.yaml + SKILL.md, projected into skills
workflows/<name>/        package.yaml + workflow YAML, projected into workflow-definitions
channels/<name>/         package.yaml + Go source, served over channel.v1 (email)
forge/<name>/            package.yaml + Go source, served over forge.v1 (github, gitea)
playbooks/<name>/        package.yaml + EDA playbook YAML, projected into eda-playbooks
profiles/<name>/         package.yaml + agent profile YAML, projected into agent-profiles
sdk/                     generated surface stubs and the Serve helper
scripts/pack.sh          build one package and push it to a registry
scripts/publish.sh       pack every package and publish the signed catalogue

A surface's contract is the gRPC service in archie-core's proto/<surface>/v1. Regenerate sdk/ from it with buf generate ../archie-core/proto --path ../archie-core/proto/<surface>. An extension can be written in any language; the Go SDK is a convenience.

Safety

An extension runs with the operator's accounts and talks to the outside world, so every one of them holds to these before it ships:

  • Inbound is authenticated before it is acted on. Identity comes only from something the extension or a trusted upstream verified (a provider's DMARC/DKIM result, a host-verified webhook signature), never from a field the sender writes. Unauthenticated input is dropped.
  • Protocols come from maintained libraries (go-imap, go-smtp, go-github, the Gitea SDK). No hand-written protocol code.
  • No listening ports. An extension dials out; inbound reaches it through the host.
  • Operator data outside the extension's job is left untouched. It changes only what it acted on (the email channel marks only routed mail read).
  • Authority is declared in package.yaml (env, egress hosts), and nothing else is assumed. Input that reaches a CLI is validated so it cannot become a flag.
  • The security check has a table test covering forged and wrong-party input.

Publish and install

Every push to main packs each package to ghcr.io/samcharles93/archipelago and publishes the catalogue that lists them, signed with the ARCHIPELAGO_CATALOGUE_KEY secret. archie-core trusts that catalogue's key, so its Extensions page lists every package with an Install button.

For a package under development, pack it to a local registry and install it by reference:

scripts/pack.sh secret-engines/bws localhost:5001/bws:1.0.0   # prints the digest

Then accept the authority the package declares, and enable it. An extension runs only while all three hold. A data package (no main.go) needs only the install: its files are projected into the matching resource and withdrawn when the package is removed.

Platform: linux/amd64.

S
Description
No description provided
Readme
898 KiB
0 Stars 0 Watchers 0 Forks
Languages
Go 98.4%
Shell 1.6%