hf-layer-package-jobs

name	hf-layer-package-jobs
description	Use when changing mesh-llm automation or CLI flows that discover Hugging Face GGUF models, plan CPU Hugging Face Jobs for layer-package splitting, estimate max cost, or publish skippy layer packages/catalog entries.
metadata	{"short-description":"Maintain HF layer package job automation"}

HF Layer Package Jobs

Use this skill for the models package CLI, the model-package crate, and the daily Unsloth queue workflow.

Workflow

1. Keep model refs in colon-selector form such as unsloth/Qwen3-8B-GGUF:Q4_K_M; do not split the quant into a separate --quant argument for generated job inputs.
2. Treat package submission as spend-bearing. The default behavior must be a dry run that prints the resolved package plan, effective timeout, selected HF Jobs hardware, and maximum cost. Require --confirm before submitting jobs.
3. Splitting is CPU and I/O bound. The HF Jobs hardware does not need enough RAM or VRAM to hold the full model; use CPU hardware suitable for running the splitter/build and scale timeout/cost estimates with model file size.
4. If the bucket script is stale during a confirmed submission, update it automatically before queuing jobs. Dry runs should avoid side effects.
5. The GitHub workflow should default to dry run. When confirmed, it should pass --confirm, submit at most the requested number of jobs, wait for every submitted HF Job, and fail if any job finishes unsuccessfully.
6. Prefer family-diverse candidate ordering after ranking by selected quant size, so one run does not consume the whole queue on a single model family.

Validation

Run Rust formatting and the focused package checks before committing:

cargo fmt --all -- --check
cargo test -p model-package
cargo check -p mesh-llm-host-runtime

For behavior smoke tests, use a tiny dry run first:

cargo run -p model-package --bin queue-unsloth-layer-packages -- --max-jobs 1 --recent-limit 3 --popular-limit 3 --dry-run