chore(rivet,ci): triage #443 (SR-53) + remove vestigial Dagger (closes #448)

[avrabe]

Two housekeeping items from the tracker.

#448 — remove vestigial Dagger (ci: commit)

A complete check found Dagger is installed, PATH'd, cached and env-configured but never invoked:

• no dagger call/run/query anywhere in the repo;
• dagger-sdk is not a Cargo dependency (absent from Cargo.lock);
• cargo-kiln / kiln-build-core reference dagger zero times, so the cargo-kiln coverage / cargo-kiln docs steps the setup wraps don't use it.

Removed across publish.yml (CLI install, Docker-for-Dagger, version check, PATH exports, DAGGER_* env), ci.yml (three ~/.cache/dagger cache steps that cache a never-written dir + commented dagger_sdk log line + two if: false PlantUML steps predicated on the non-existent "CheckDocsStrict Dagger pipeline"), and security-audit.yml (stale pkg:cargo/dagger-sdk@0.11.10 allow-list entry). Net −58 lines; the actual cargo-kiln commands are unchanged; all three workflows still parse.

Also found, left for your call: deploy-docs-sftp.yml.example references cargo xtask publish-docs-dagger (xtask is a removed legacy component) — but it's an .example template, not an active workflow, so I didn't touch it.

#443 — SR-53 triage (chore(rivet): commit)

Lands the arg-arity fabricated-success bug (kilnd zero-fills missing params and reports the wrong result as ✓ success) as rivet SR-53, release: v0.4.3. The code fix is in flight on a separate branch (fix/sr-53-...).

rivet validate: 0 errors.

🤖 Generated with Claude Code

[github-actions]

🔍 Build Diagnostics Report

Summary

Metric	Base Branch	This PR	Change
Errors	0	0	0
Warnings	5	5	0

🎯 Impact Analysis

Issues in Files You Modified

• 0 new errors introduced by your changes
• 0 new warnings introduced by your changes
• 0 total errors in modified files
• 0 total warnings in modified files
• 0 files you modified

Cascading Issues (Your Changes Breaking Other Files)

• 0 new errors in unchanged files
• 0 new warnings in unchanged files
• 0 unchanged files now affected

Note: "Cascading issues" are errors in files you didn't modify, caused by your changes (e.g., breaking API changes, dependency issues).

✅ No Issues Detected

Perfect! Your changes don't introduce any new errors or warnings, and don't break any existing code.

---

📊 Full diagnostic data available in workflow artifacts

🔧 To reproduce locally:

# Install cargo-kiln
cargo install --path cargo-kiln

# Analyze your changes
cargo-kiln build --output json --filter-severity error
cargo-kiln check --output json --filter-severity warning

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!