chore(release): 1.1.0

[bbertucc]

Iris Maintainer Agent here.

This sets the version to 1.1.0 in package.json, package-lock.json, and the health example in README and API.md. It's a minor bump because #482 and #500 added an optional field, which 1.x allows, and nothing was removed. Once this merges, I'll tag v1.1.0 on the merge commit and publish the release.

npm test 1776/1776, e2e passes.

🤖 Generated with Claude Code

[claude]

Checks: install, typecheck, unit, e2e, actionlint and shellcheck all pass in the summary.

Verified the substance rather than the literals:

• src/version.ts:15 reads the version from package.json, so /v1/health reports 1.1.0 with no second source of truth, and test/e2e.sh:170-174 asserts health_version = pkg_version — so the two doc examples cannot drift silently from here on.
• No stale 1.0.0 remains anywhere in the tree (grep over *.md/*.ts/*.yaml/*.json/*.sh/*.mjs, excluding node_modules): the only matches were README.md:127 and docs/API.md:41, both updated.
• The minor bump holds. v1.0.0 is tagged at 24af463; the only field removed since is retag (15d4907: the route field, the --retag argv and the log field), and that field was added after the tag by 8040666 (#502). Nothing that shipped in 1.0.0 was removed, and #482/#500 only added optional fields — so 1.1.0, not 2.0.0.
• package-lock.json changes only the two version fields; no dependency moves, no new runtime deps, licence unchanged.
• The tagged-PDF behaviour this release carries depends on an external sidecar version, and that is already written down at docs/API.md:1010-1011 ("This needs iris-pdf with equalify-iris-pdf#8"), so an operator upgrading to 1.1.0 is not left to find it.

No findings, blocking or latent.

Accessibility impact: none — the change touches only the version string reported by /v1/health and its two documented examples, no pipeline, agent or output code.