docs: fix examples README, README TS imports, and init-template skills (schedule/npm/ruby/gha-404)

[markovejnovic]

Summary

Fixes stale API-surface references in user- and agent-facing docs that the DSL evolution left behind. The published surface changed (npm/bun folded into a unified js toolchain, the Ruby toolchain removed, the schedule trigger + croniter dropped, the TS package renamed to @harmont/hm), but several docs and embedded hm init skill templates still advertised the old API. Agents and users following them hit AttributeErrors, unknown-arg errors, dead doc rows, and 404 fetches.

Changes (single commit, 5 files):

• examples/README.md — hm.npm/hm.bun/hm.ruby → hm.js.project(...) (bun → runtime="bun"); drop the deleted [ruby](./ruby) table row; replace the invalid hm run <slug> --local / hm run ci --local with hm run (local Docker is the default backend) plus a --backend cloud note.
• README.md — TypeScript quickstart imports harmont / harmont/toolchains → @harmont/hm / @harmont/hm/toolchains (the published name). Python example left as-is (the PyPI package is still harmont).
• skill_write_pipeline.md + committed .claude/skills/write-pipeline/SKILL.md — drop the removed schedule trigger from the triggers guidance; npm → js in the toolchain list; remove stale Ruby references so the committed dogfood copy byte-matches the embedded template.
• skill_convert_gha.md — on: schedule now maps to "No local DSL trigger" (a Harmont Cloud concern) instead of a bogus "Direct mapping"; add schedule to the real-gaps list; hm.npm → hm.js in the setup-* mapping; remove the dead WebFetch of the 404 docs.harmont.dev/examples/github-actions.md.

Findings addressed

• examples-readme-dead-toolchain-calls-1
• examples-readme-local-flag-1
• ts-pkg-rename-readme-1
• skills-schedule-removed-1
• skills-npm-toolchain-1
• claude-skill-ruby-stale-1
• skills-gha-example-404-1

Verification evidence

Claims in the edited docs were checked against the current code in the branch:

• hm.js.project(...) exists and accepts runtime →
  grep -n "def project" crates/hm-dsl-engine/harmont-py/harmont/_js.py → 233: def project( with runtime: Runtime | None = None.
• runtime="bun" is valid →
  _js.py:38 Runtime = Literal["node", "bun", "deno"].
• Ruby toolchain removed →
  ls crates/hm-dsl-engine/harmont-py/harmont/_ruby.py → No such file or directory.
• schedule trigger removed →
  grep -in "schedule" crates/hm-dsl-engine/harmont-py/harmont/triggers.py → no matches.
• TS package renamed →
  crates/hm-dsl-engine/harmont-ts/package.json:2 "name": "@harmont/hm".
• --backend cloud flag exists (and --local is gone, so the old hm run ... --local is correctly replaced) →
  crates/hm/src/cli/run.rs:59 pub backend: Option<String>, docstring docker (default) ... cloud submits it to Harmont Cloud.
• Committed dogfood skill byte-matches the embedded template →
  diff crates/hm/src/commands/init_templates/skill_write_pipeline.md .claude/skills/write-pipeline/SKILL.md → IDENTICAL.

Docs-only change to Markdown files; no Rust/Python/TS source touched, so no compile/test impact.

Judge verdict

Approved. No blocking issues. Implementer verification passed.

---

Generated by the Harmont release-readiness workflow (automated; needs human review before merge). 🤖