Skip to content

feat: capability-based agent composition and architecture #520

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
yacosta738 merged 13 commits into from
Apr 12, 2026
Merged

feat: capability-based agent composition and architecture #520

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
13 commits
Select commit Hold shift + click to select a range
d1fab7b
fix(dashboard): add WCAG 2.1 AA accessibility improvements
yacosta738 Apr 12, 2026
987576b
feat(agent-runtime): add capability-based agent composition
yacosta738 Apr 12, 2026
223dac2
ci(release): add beta release workflow and update publishing logic
yacosta738 Apr 12, 2026
797e5dc
chore: add test-results and .playwright-mcp to gitignore
yacosta738 Apr 12, 2026
3f41e2d
Merge branch 'main' into feature/capability-architecture
yacosta738 Apr 12, 2026
24e1f39
Merge branch 'refs/heads/main' into feature/capability-architecture
yacosta738 Apr 12, 2026
c96a47a
feat: add chat navigation item and improve accessibility features
yacosta738 Apr 12, 2026
749a2b2
fix: apply code review fixes from PR feedback
yacosta738 Apr 12, 2026
95719d0
chore: sync Cargo.lock files after version bump
github-actions[bot] Apr 12, 2026
ffebece
fix: exclude CSS import file URLs from lychee link checker
yacosta738 Apr 12, 2026
a85c238
fix(runtime): own String keys in HashMap for case-insensitive uniquen…
yacosta738 Apr 12, 2026
48881c2
📝 CodeRabbit Chat: Add unit tests for PR changes
coderabbitai[bot] Apr 12, 2026
e8712ef
style: fix spotless formatting violations in .github/workflows/README…
yacosta738 Apr 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
137 changes: 92 additions & 45 deletions .agents/journal/scribe-journal.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,45 +1,92 @@
# Scribe Journal

## 2025-05-15 - AI Providers Documentation - Completed

**Verification:** I have thoroughly inspected `clients/agent-runtime/src/providers/mod.rs` and individual provider implementations (e.g., `gemini.rs`, `anthropic.rs`) to identify all supported providers and their environment variables.
**Changes:**
- Updated `clients/web/apps/docs/src/content/docs/clients/agent-runtime/providers/index.mdx` (EN) and `clients/web/apps/docs/src/content/docs/es/clients/agent-runtime/providers/index.mdx` (ES).
- Added missing providers: `OpenAI Codex`, `Synthetic`, `OpenCode Zen`, `Amazon Bedrock`, `LM Studio`.
- Updated environment variables for `Anthropic` (`ANTHROPIC_OAUTH_TOKEN`), `GitHub Copilot` (`GH_TOKEN`), and `Google Gemini` (`GOOGLE_API_KEY`).
- Added "Advanced Authentication" section covering OAuth/CLI reuse for Gemini, Codex, and Copilot, and setup tokens for Anthropic.
**Validation:** Ran `make docs-web-build` and `make docs-web-check`.
**Notes:**
- Confirmed `gemini-cli` OAuth token support in `gemini.rs`.
- Confirmed `ANTHROPIC_OAUTH_TOKEN` support in `mod.rs`.
- Maintained strict bilingual parity between English and Spanish versions.

## 2025-05-18 - Tools Reference Documentation - Completed

**Verification:** Audited `clients/agent-runtime/src/tools/` to identify all built-in tools, their parameters, and security tiers. Verified the integration of `agent-browser` and MCP.
**Changes:**
- Created a comprehensive Tools Reference section in both English and Spanish (14 new files).
- Categorized tools into: Core (shell, file_read/write), Web (browser, http_request, search), Memory (store/recall/forget), Automation (git, cron, schedule), Media (screenshot, image_info), and MCP.
- Documented Security Operation Tiers (Safe/Read-Only vs. Risk/Action-Bearing).
- Updated index pages in `docs/clients/agent-runtime/` and `docs/es/clients/agent-runtime/` to link to the new Tools Reference.
**Validation:**
- Ran `make docs-check` and `make docs-build`. 58 pages built successfully.
- Visual verification performed via Playwright for both English and Spanish layouts.
**Notes:**
- Confirmed strict 1:1 parity between `en/` and `es/` directories.
- Technical details like `mcp.<server>.<tool>` naming convention and `agent-browser` requirements are now documented.

## 2025-05-22 - Automation and Hardware Tools Reference - Completed

**Verification:** Audited `clients/agent-runtime/src/tools/` and `clients/agent-runtime/src/peripherals/` to verify parameters and security tiers for all mission-critical tools. Confirmed `delegate` execution modes (OneShot/Session) and verified the full set of `cron_*` tools.
**Changes:**
- Updated `automation.md` (EN/ES) to include `delegate`, `composio`, and complete `cron_*`/`schedule` reference.
- Created `hardware.md` (EN/ES) documenting board discovery (`hardware_board_info`), memory operations (`hardware_memory_map`, `hardware_memory_read`), and peripheral control (`gpio_read`, `gpio_write`, `arduino_upload`).
- Updated `index.mdx` (EN/ES) to include Hardware category and update tool counts/examples.
**Validation:**
- Ran `pnpm --dir clients/web --filter @corvus/locales test` (Passed).
- Ran `./gradlew :web:docsCheck` (Passed: Astro check, Biome lint, Metadata validation).
**Notes:**
- Maintained strict 1:1 parity between English and Spanish.
- Confirmed that `gpio_read`/`gpio_write` are available on both RPi (native) and Uno Q (bridge).
- Documented `arduino_upload` requirements (`arduino-cli`).
# Scribe Documentation Journal

## 2026-04-12 - Full Documentation Accuracy Audit - Complete

**Verification:** Systematic comparison of all documentation files in `clients/web/apps/docs/src/content/docs/` (both en/ and es/) against the actual codebase implementation in `clients/agent-runtime/`, `modules/cerebro/`, and root-level build/tooling files.

### Structure Assessment
- **Bilingual Parity:** ✅ Perfect. 53 files in English (root-level default), 53 files in Spanish (`es/`). 1:1 file mapping with identical directory structures.
- **Note:** The documentation does NOT use an `en/` directory. English docs live at the root of `docs/`, with `es/` as the translation overlay. This is consistent with Starlight's default locale behavior.

### CLI Reference (`guides/cli-reference.md`)
- **Accuracy:** ✅ High. All documented commands, subcommands, and flags verified against `clients/agent-runtime/src/main.rs` and `composer.rs`.
- **Verified commands:** onboard, agent, code, daemon, gateway, service, doctor, status, cron, models, providers, auth, skills, integrations, channel, hardware, peripheral, migrate, update, cost.
- **Dashboard activation codes:** DASH-001 through DASH-004, DASH-999 — all documented and verified in the onboard/dashboard code.
- **`make dev-up`**: Verified exists at Makefile:308.

### Cerebro CLI (`cerebro/cli-reference.md`)
- **Accuracy:** ✅ Fully implemented. Verified at `modules/cerebro/src/bin/cerebro.rs`. Two binaries: `cerebro` (full CLI) and `cerebro-serve` (lightweight server). Commands `serve` and `migrate import/validate` match docs exactly.

### Cerebro Configuration (`cerebro/configuration.md`)
- **Accuracy:** ✅ All config fields, env vars, storage modes, and TUI settings verified against `modules/cerebro/` source. `remote_surreal` correctly marked as "not yet implemented" in both docs and code.

### Architecture (`clients/agent-runtime/architecture.md`)
- **Accuracy:** ✅ High. All components verified as implemented:
- 22+ providers ✅ (including all regional variants and custom endpoints)
- 14 channels ✅ (CLI, Telegram, Discord, Slack, WhatsApp, Signal, iMessage, Matrix, DingTalk, QQ, Lark, Email, IRC, Mattermost)
- 32+ tools ✅
- 4 memory backends ✅ (sqlite, lucid, markdown, none)
- 5 observability backends ✅ (noop, log, prometheus, otel, multi)
- Security: Landlock ✅, Bubblewrap ✅, Firejail ✅ (verified in `security/firejail.rs`), Noop ✅
- **Minor note:** Docs mention "Firejail" in sandboxing section — this IS implemented (77 matches in code). The mermaid diagram says "landlock/firejail/bubblewrap" which is accurate.
- **Capability profiles** (full, code, lite) — verified in bootstrap code.

### Tools Reference (`clients/agent-runtime/tools/`)
- **Accuracy:** ✅ All tool category pages verified against actual tool implementations in `src/tools/`.
- **Security tiers** (Read-Only vs Action-Bearing) — verified against `security/policy.rs` risk classification.
- **MCP tool runtime** — verified in `tools/mcp/`, correctly documented as gated by `mcp.enabled`.

### Providers (`clients/agent-runtime/providers/index.mdx`)
- **Accuracy:** ✅ All 22+ providers verified. LM Studio confirmed at `providers/mod.rs:527`. Gemini OAuth and env vars (`GEMINI_API_KEY`, `GOOGLE_API_KEY`) verified in `providers/gemini.rs`. Regional providers (Moonshot, GLM, MiniMax, Qwen, Qianfan, Z.AI) all confirmed.

### Model Routing (`guides/model-routing.md`)
- **Accuracy:** ✅ `[[model_routes]]` and `[query_classification]` config structures verified against `config/schema.rs`. `corvus doctor` validation warnings verified in doctor module code. `allow_image_input` gate verified.

### Sandbox Isolation (`guides/runtime-sandbox-isolation.md`)
- **Accuracy:** ✅ All sandbox backends verified: landlock, firejail, bubblewrap, docker, none. `require = true` fail-closed behavior verified. Computer-use sidecar health check (`GET /v1/health`) verified. Audit log fields match implementation.

### Getting Started (`guides/getting-started.md`)
- **Accuracy:** ✅ Prerequisites match AGENTS.md. `make setup`, `make build`, `make run`, `make test` all verified in Makefile. Dashboard activation flow verified.

### SurrealDB Guide (`guides/surrealdb.md`)
- **Assessment:** This is a general operational guide for running SurrealDB with Docker Compose. Not specific to Corvus implementation but technically accurate for SurrealDB v3. No discrepancies found.

### Configuration Options (`guides/configuration.md`)
- **Assessment:** ⚠️ **PARTIAL COVERAGE**. This document focuses heavily on Gradle properties, version catalogs, and MCP configuration. It does NOT cover the full `config.toml` schema for the agent runtime (which is extensive — 30+ sections). The MCP section is accurate. **Recommendation:** This doc should be expanded or split to cover the agent runtime's full configuration surface.

### Customization (`guides/customization.md`)
- **Assessment:** ⚠️ **OUTDATED**. References `com.profiletailors` as the package namespace and mentions "This repository was created from a Gradle template." This is legacy template language. The "Platform Direction" section mentions "Kotlin + Spring Boot (WebFlux + Coroutines)" and "Neo4j for graph memory" which do NOT appear to be implemented in the current codebase. The actual architecture is Rust-based agent-runtime with Kotlin Multiplatform clients. **This section needs review and likely significant updates.**

### Features Checklist (`guides/features.md`)
- **Assessment:** ⚠️ **PARTIALLY OUTDATED**. Lists modules as `apps/composeApp`, `apps/androidApp`, etc. but the actual directory structure uses `clients/` prefix (e.g., `clients/composeApp`). Mentions "apps/agent-runtime-rust" but actual path is `clients/agent-runtime`. Missing several implemented features: cost tracking, update system, skills system, cron/scheduler, hardware peripherals, model routing, computer-use sidecar, tunnel providers. **Needs comprehensive update.**

### Development Procedures (`guides/development.md`)
- **Accuracy:** ✅ Makefile commands verified. `make setup`, `make run`, `make build`, `make test`, `make check`, `make format`, `make clean` all present. Documentation commands (`make docs-web-build`, etc.) verified against Makefile.

### Structure (`guides/structure.md`)
- **Accuracy:** ✅ Directory structure matches reality. `clients/`, `modules/`, `gradle/` all correctly described.

### Issues Summary

| Severity | File | Issue |
|----------|------|-------|
| 🔴 HIGH | `guides/customization.md` | References Spring Boot/Neo4j architecture not in codebase; legacy template language |
| 🔴 HIGH | `guides/features.md` | Wrong module paths (`apps/` vs `clients/`); missing 10+ major features |
| 🟡 MEDIUM | `guides/configuration.md` | Only covers Gradle/MCP; missing full agent runtime config reference |
| 🟢 LOW | `cerebro/` docs | All accurate, but lastReviewed date (2026-04-02) is recent — no action needed |

### Remediation (2026-04-12)

All three identified issues have been fixed:

1. **`guides/customization.md`** — ✅ Fixed. Removed Spring Boot/Neo4j references. Updated with current architecture (Rust agent runtime, KMP clients, Cerebro, web apps). Corrected VERSION to 3.0.0. Added `includeProjects` module registration guide. Both en/es synced.
2. **`guides/features.md`** — ✅ Fixed. Corrected all paths from `apps/` to `clients/`. Expanded from basic checklist to comprehensive coverage: 22+ providers, 14 channels, 32+ tools, memory backends, infrastructure, security, hardware, tunnels. Both en/es synced.
3. **`guides/configuration.md`** — ✅ Improved. Added full agent runtime config reference covering autonomy, security/sandbox, runtime, gateway, memory, agent profiles, model routing, multimodal/audio, scheduler, MCP, observability, cost, updates, skills, and env var overrides. Both en/es synced.

### Validation Results
- `make docs-check` — ✅ PASSED (astro check + biome + metadata validation: 0 errors, 0 warnings, 8 files validated)
- `make docs-build` — ✅ PASSED (80 pages built, search index generated, no broken links)

### Notes
Comment on lines +7 to +90
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot Apr 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Fix markdown heading spacing to satisfy MD022.

Several headings (for example Line 7, Line 11, Line 17, and others) are missing required surrounding blank lines. This will keep markdownlint noisy and can break consistent rendering in some processors.

Suggested pattern 
 ### Structure Assessment
+
 - **Bilingual Parity:** ✅ Perfect. 53 files in English (root-level default), 53 files in Spanish (`es/`). 1:1 file mapping with identical directory structures.
🧰 Tools
🪛 LanguageTool

[style] ~80-~80: Consider using a different verb for a more formal wording.
Context: ... All three identified issues have been fixed: 1. guides/customization.md — ✅ ...

(FIX_RESOLVE)

🪛 markdownlint-cli2 (0.22.0)

[warning] 7-7: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)

[warning] 11-11: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)

[warning] 17-17: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)

[warning] 20-20: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)

[warning] 23-23: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)

[warning] 34-34: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)

[warning] 39-39: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)

[warning] 42-42: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)

[warning] 45-45: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)

[warning] 48-48: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)

[warning] 51-51: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)

[warning] 54-54: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)

[warning] 57-57: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)

[warning] 60-60: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)

[warning] 63-63: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)

[warning] 66-66: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)

[warning] 86-86: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)

[warning] 90-90: Headings should be surrounded by blank lines
Expected: 1; Actual: 0; Below

(MD022, blanks-around-headings)

🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In @.agents/journal/scribe-journal.md around lines 7 - 90, Several Markdown
headings in scribe-journal.md (e.g., "Structure Assessment", "CLI Reference
(`guides/cli-reference.md`)", "Cerebro CLI (`cerebro/cli-reference.md`)" and
others) are missing required surrounding blank lines and trigger MD022; insert a
single blank line above and below each top-level and subheading so every heading
is separated from adjacent content (ensure lists and preceding paragraphs end
with a blank line before the heading and add a blank line after the heading
before the following paragraph or list). Locate headings by their exact text
(e.g., "Structure Assessment", "CLI Reference (`guides/cli-reference.md`)",
"Cerebro CLI (`cerebro/cli-reference.md`)", etc.) in scribe-journal.md and
normalize spacing consistently across the file to satisfy MD022.

- Glossary: "Firejail" = Linux user-space sandbox (confirmed implemented). "Landlock" = Linux kernel-level sandbox (confirmed). "Cerebro" = standalone MCP memory service in `modules/cerebro/` (confirmed).
- Remaining gap: `cost` command subcommands (`summary`, `history`, `reset`) exist in code but are not yet in the CLI reference doc. Low priority.
62 changes: 48 additions & 14 deletions .github/workflows/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,8 @@ This directory contains all GitHub Actions workflows for the Corvus monorepo. Wo
| **Publishing** | `publish-release.yml` | Attach stable artifacts to canonical GitHub Release | `release.published` |
| **Publishing** | `publish-snapshot.yml` | Publish Gradle/Maven snapshots only | Manual, daily schedule |
| **Publishing** | `release-please.yml` | Create repo-wide release PRs, tags, and canonical GitHub Releases | Push to `main`, manual |
| **Publishing** | `_publish.yml` | Reusable publish workflow | Called by other workflows |
| **Publishing** | `release-please-beta.yml` | Create beta prerelease PRs, tags, and canonical GitHub Releases | Push to `beta`, manual |
| **Publishing** | `_publish.yml` | Reusable stable/beta/snapshot publish workflow | Called by other workflows |
| **Automation** | `auto-fix-lockfile.yml` | Auto-update lockfiles | Daily schedule, manual |
| **Automation** | `fix-renovate.yml` | Fix lockfiles for Renovate PRs | Comment `/fix-lock` on PR |
| **Repo Mgmt** | `git-issue-labeled.yml` | Auto-comments/closes labeled issues | Issue labeled |
Expand Down Expand Up @@ -179,6 +180,8 @@ Code Scanning.

release-please is the canonical owner of the stable GitHub Release and release notes.
\_publish.yml exists to attach artifacts to that existing release after `release.published`.
`release-please-beta.yml` owns the canonical beta branch prerelease PRs, tags, GitHub Releases,
and beta release notes.

### `publish-release.yml` - Release Publishing

Expand Down Expand Up @@ -240,6 +243,33 @@ Calls the reusable `_publish.yml` workflow with:

---

### `release-please-beta.yml` - Beta Release PR Automation

**Purpose**: Opens or updates the single repo-wide beta prerelease PR from `beta` and owns the
canonical beta prerelease tag, GitHub Release, and release notes.

**Triggers**:

- Push to `beta`
- Manual trigger (`workflow_dispatch`)

**What it does**:

- Runs release-please with `release-please-beta-config.json`
- Creates or updates a beta prerelease PR with shipped-artifact beta version bumps
- Writes diagnostics to the workflow summary, including the beta manifest baseline and action outputs
- On merge, creates the canonical `vX.Y.Z-beta.N` tag and canonical GitHub prerelease
- Publishes canonical beta GitHub Release notes, then hands beta artifact publication to `_publish.yml`

**Beta contract**:

- `release-please-beta.yml` is the canonical owner of beta release PRs, beta tags, beta GitHub Releases, and beta notes.
- Beta releases publish the same shipped artifact set as stable releases.
- npm beta releases use the `beta` dist-tag instead of `latest`.
- Beta Docker publication uses the exact prerelease version plus the moving `beta` tag, and never overwrites stable aliases like `latest`.

---

### `release-please.yml` - Release PR Automation

**Purpose**: Opens or updates the single repo-wide stable release PR from `main` and owns the
Expand Down Expand Up @@ -274,16 +304,18 @@ canonical stable tag, GitHub Release, and release notes.

### `_publish.yml` - Reusable Publishing Workflow

**Purpose**: Internal reusable workflow for publishing release/snapshot artifacts.
**Purpose**: Internal reusable workflow for publishing stable, beta, and snapshot artifacts.

**Called by**: `publish-release.yml`, `publish-snapshot.yml`
**Called by**: `publish-release.yml`, `publish-snapshot.yml`, `release-please-beta.yml`

Comment thread
coderabbitai[bot] marked this conversation as resolved.
**Inputs**:
| Input | Type | Default | Description |
|-------|------|---------|-------------|
| `release` | boolean | required | Whether the workflow is in stable release mode |
| `release_tag` | string | empty | Canonical stable tag to validate and publish against |
| `release_id` | string | empty | Existing GitHub Release id for asset upload |

| Input | Type | Default | Description |
| ------------- | ------- | -------- | ----------------------------------------------------- |
| `release` | boolean | required | Whether the workflow is in release mode |
| `prerelease` | boolean | `false` | Whether the release is a beta prerelease |
| `release_tag` | string | empty | Canonical release tag to validate and publish against |
| `release_id` | string | empty | Existing GitHub Release id for asset upload |

**Secrets Required**:

Expand All @@ -302,17 +334,19 @@ canonical stable tag, GitHub Release, and release notes.
2. 🧭 Validates explicit stable release context (`release_tag`, `release_id`) against the existing GitHub Release
3. 👻 Publishes to Maven Central using Gradle
4. 🦀 Publishes Rust crate to crates.io (release only)
5. 📦 Publishes shipped runtime npm packages to npm (release only)
6. 🐳 Builds and publishes multi-arch runtime Docker image to Docker Hub + GHCR (release only)
7. 📊 Builds and publishes multi-arch dashboard Docker image to Docker Hub + GHCR (release only)
5. 📦 Publishes shipped runtime npm packages to npm using `latest` for stable or `beta` for prereleases
6. 🐳 Builds and publishes multi-arch runtime Docker image to Docker Hub + GHCR with stable or beta-safe tags
7. 📊 Builds and publishes multi-arch dashboard Docker image to Docker Hub + GHCR with stable or beta-safe tags
8. 🚀 Attaches assets to the existing canonical GitHub Release

**Key Points**:

- ⚠️ Warning: Do not use never-expiring User Token for Maven Central
- `release-please` owns the canonical public GitHub Release and canonical stable release notes
- `release-please-beta.yml` owns the canonical public GitHub prerelease and canonical beta release notes
- `_publish.yml` only uploads assets with `gh release upload --clobber`
- Stable publication fans out from `release.published`
- Beta publication fans out from `release-please-beta.yml`
- Stable npm publishing excludes `corvus-cli` because it is internal/private
- Windows ARM64 is intentionally unsupported for stable npm publication

Expand Down Expand Up @@ -664,9 +698,9 @@ if: >
## 🔄 Workflow Dependencies

```
publish-release.yml ─┐
├──> _publish.yml (reusable)
publish-snapshot.yml ┘
publish-release.yml ────────┐
release-please-beta.yml ├──> _publish.yml (reusable)
publish-snapshot.yml ───────┘

Other workflows call dallay/common-actions:
- cleanup-cache.yml
Expand Down
Loading
Loading