feat: v1.7.0 — workflow archive / unarchive (reversible alternative to delete)

[trngthnh369]

Closes the gap the user hit: n8nctl could only delete workflows, permanently.

n8nctl workflow archive <id>     # reversible; forces the workflow inactive
n8nctl workflow unarchive <id>   # restores it, still inactive

Maps to the n8n public API POST /workflows/{id}/archive / /unarchive
(n8n-io/n8n#27513, merged 2026-03-27).
Both follow the existing activate.ts shape and support --dry-run.

The version gap this has to handle

The instance this was developed against (n8n 1.122.5) returns isArchived on the
workflow model but 404s on POST /workflows/{id}/archive — the field shipped before
the endpoints did. So a 404 here is ambiguous: missing workflow, or missing endpoint?

archiveWithVersionGuard resolves it on the error path only (no extra request on the
happy path):

Probe GET /workflows/{id}	Meaning	Result
404 (confirming)	workflow genuinely gone	rethrow the original 404
200	endpoint is what's absent	upgrade hint citing #27513
anything else (401, 5xx, network)	probe proves nothing	surface that error

That last row came out of review: a bare catch would have reported "workflow not found —
verify the ID" for what is really an auth or connectivity fault, blaming the user for the
wrong thing.

unarchive --dry-run reuses the workflow it already fetched to flag the documented 400 when
the target is not archived, rather than reporting success for a call that cannot succeed.

Verified, not assumed

• Live against n8npc 1.122.5: archive/unarchive 404 while GET returns 200 (checked at
  raw HTTP, confirming the guard's GET-200 branch actually fires); DELETE still hard-deletes
  there; --dry-run mutates nothing. Scratch workflow created and cleaned up — no production
  workflow was archived.
• Source, not guesswork: WorkflowService.archive sets active=false; archiving an
  already-archived workflow is a 200 no-op (skipArchived); unarchiving a non-archived one
  throws BadRequestError → 400. The user-facing messages state what the code does.
• 12 new tests (502 total), coverage gate green, npm audit --omit=dev clean, docs
  drift gate clean.

Deliberately out of scope

--json does not change these commands' output — they print a status line, exactly like
activate / deactivate / delete. Review suggested wiring printData in; I left it alone
because doing it for archive only would make it the odd one out among the mutation verbs.
Wiring --json through all of them is a worthwhile separate change.

Endpoint contracts + the version gap are recorded in scripts/SESSION_REST_CONTRACT.md.

Not tagged/published — v1.7.0 is bumped in package.json + CHANGELOG.md, but tagging
(which triggers the npm release) is left for you to decide.

🤖 Generated with Claude Code