5ae4ea4c84
* feat(#1105): add external-job capability (SLURM scheduler-adapter producer half) The async external-job consumer half (#1165) shipped long ago: the core loop reads .planning/async-jobs/<job>.json manifests and treats a non-terminal one as the legal external_job_waiting half-state. The PRODUCER half (#1164) was the remaining unimplemented piece of #1105. This adds the producer as a default-off capability: - capabilities/external-job/ — capability.json (execute:wave:post -> executor, plan:post -> planner contributions, external_job.* config keys, default-off) + fragments teaching runtime-budget classification and externalization. - src/external-job.cts -> gsd-core/bin/lib/external-job.cjs — pure producer module: SLURM state -> manifest-status map (no guessing), manifest build/validate (versioned stability contract), sbatch/squeue/sacct parsers, and a fail-closed manifest writer (refuses a second non-terminal job for a plan_id already in flight; refuses to clobber a malformed manifest). fs/clock seams for deterministic tests. - scripts/slurm-adapter.cjs — operator CLI (submit/poll/show) wrapping bounded sbatch/squeue/sacct subprocesses; surfaces manifest commands for confirmation and never auto-runs them (trust boundary). - tests/external-job.test.cjs — 23 behavioral + fast-check property tests. - docs/reference/long-running-operations.md + docs/how-to/async-external-jobs.md. - CONTEXT.md glossary entry for the External-job Capability. - Regenerated capability-registry.cjs; pruned the now-stale test-file-count allowlist entry (external-job is at the 2-file cap). * chore(#1105): backfill PR number in changeset * fix(#1105): sync capability artifacts + update registry shape-pin tests gsd-test caught that adding the external-job capability requires its dependent artifacts regenerated and its registry-shape drift absorbed: - sync-manifest-versions: stamp 1.7.0-rc.2 into capability.json (was 1.0.0). - gen-capability-matrix --write: regenerate docs/reference/capability-matrix.md. - gen-inventory-manifest --write: regenerate docs/INVENTORY-MANIFEST.json. - check-gap-analysis-plan-post-e2e: plan:post now has 1 contribution (external-job planner fragment) instead of 0. - execute-wave-post-gate-pipeline-e2e: execute:wave:post now has 2 contributions (mempalace + external-job) instead of 1. * fix(#1105): regenerate capability-registry after version stamp sync-manifest-versions re-stamped external-job/capability.json from 1.0.0 to 1.7.0-rc.2 after the last registry regeneration, leaving the committed capability-registry.cjs stale (CI gen-capability-registry --check failed). gsd-test masked this because its setup runs the full 'npm run build' (which regenerates the registry); CI's 'npm test' pretest only runs build:lib.
25 lines
1.4 KiB
Markdown
25 lines
1.4 KiB
Markdown
<!-- external-job capability — plan:post fragment, injected into the planner (#1164). -->
|
||
|
||
## Tag runtime budgets on long tasks
|
||
|
||
For every `<task>` likely to exceed ~2 minutes of real compute, emit a
|
||
`<runtime_budget>` child element so execute can classify it:
|
||
|
||
- `<runtime_budget>quick</runtime_budget>` — under ~2 min; runs normally.
|
||
- `<runtime_budget>medium</runtime_budget>` — ~2–30 min; foreground, but with
|
||
progress expectations.
|
||
- `<runtime_budget>unknown</runtime_budget>` — runtime not yet characterized;
|
||
execute must run a first-health check and set a soft-review deadline before
|
||
trusting the child timeout. Define a progress signal and an abort condition.
|
||
- `<runtime_budget>long_compute</runtime_budget>` — legitimately over ~30–60 min
|
||
(HPC solver, model training, large simulations). Execute must **externalize**
|
||
this as an async external job (see the execute:wave:post fragment) rather than
|
||
blocking the agent turn.
|
||
|
||
For any `long_compute` task, also declare the async contract the executor will
|
||
need: the `submit_command`, the `expected_artifacts` the job must produce, and
|
||
the `verification_command` that proves the output before the plan can close.
|
||
Do not hardcode a cluster account, partition, or project path — the planner
|
||
never knows the scheduler layout; it declares the contract, the executor's
|
||
adapter fills the backend specifics.
|