yuvuResources

Public, versioned runtime resources for Yuvu.

This repository is the distribution source for:

• the adapter deployment catalog consumed by yuvuNode;
• reusable task and workflow templates consumed by yuvuCli.

It never stores credentials, deployment secrets, private keys, DSNs, or host security policy. A catalog entry describes what a deployment needs; each node's read-only local policy remains authoritative about what is allowed.

Layout

catalog/adapters.json       adapter deployment catalog
templates/**/*.yaml        reusable task/workflow templates
manifest.json               generated content manifest
cmd/build-manifest          deterministic manifest generator

Publishing

Run:

make manifest
make check

CI rebuilds the manifest in a dedicated manifest-guard step and fails when manifest.json drifts from the checked-in templates and catalog. Template, catalog, or runtime-profile changes must run make manifest and commit manifest.json together with the content change. Clients fetch the manifest over HTTPS, verify resource SHA-256 values, and retain a last-known-good local cache.

The stable manifest URL is:

https://forgejo.zuixue.site/xm/yuvuResources/raw/branch/main/manifest.json

Provenance

manifest.json is content-addressed: revision is the SHA-256 over the sorted name=sha256 lines of the catalog, every template, and every runtime profile. An identical revision therefore means a byte-identical resource set, and is the authoritative key for verifying which version a client rendered.

The committed manifest.json deliberately does not embed a git commit: a self-referential commit field cannot be both committed and byte-deterministic under the manifest-guard regenerate-and-diff gate. To map a revision to the commit that published it, resolve it from the same origin out-of-band:

https://forgejo.zuixue.site/api/v1/repos/xm/yuvuResources/commits?sha=main&path=manifest.json&limit=1

The first returned commit's sha is the publishing commit for the served manifest.json. Surfacing it alongside revision in yuvu resources and template render/show output is a yuvuCli follow-up (cross-repo); this repository guarantees revision and the per-resource sha256 values only.

Template format

schema_version: 1
name: maa/daily
kind: workflow
description: Run the standard Arknights daily workflow.
allow_overrides:
  - tasks.fight.inputs.stage
document:
  api_version: yuvu/v1
  kind: Workflow
  metadata:
    name: arknights-daily
  tasks: {}

document is either an existing Yuvu task request or workflow document. Overrides are denied unless their exact path appears in allow_overrides.

Published templates

• maa/daily - standard Arknights daily workflow.
• maaend/daily-full - official MaaEnd DailyFull routine, with reward claiming after the activity-producing tasks.
• backup/restic-retention - restic backup followed by retention and prune.
• armbian/rock5b-redroid-maintenance - reviewed Rock 5B Armbian vendor build with the Redroid kernel contract, ZFS, official Docker packages, and common maintenance tools.
• media/video-subtitle-translate - Artifact-first video to audio, Whisper SRT, segment translation, and final subtitle rendering. Intermediate S3 artifacts use task_terminal cleanup and are removed on success, failure, or cancel.
• models/heretic-transform - inspect a reviewed Hugging Face model, run a bounded non-interactive Heretic transformation, and publish the transformed model as an Adapter V3 bundle while retaining resumable checkpoints.
• smoke/heretic - validate the pinned Heretic runtime and model metadata path without downloading model weights or occupying GPU memory.
• smoke/vllm-qwen38 - starts the deployment-owned vLLM runtime and validates Qwen3.8 model discovery plus a thinking-mode chat completion.