[jake-b-omni]

onex dashboard serves a pinned bundle. v1.1.6 was tagged at 818fa47a (#375), one commit before #376 (OMN-20753, Runs status and cost), so no published bundle carries that fix. This PR gives it a version to tag.

Scope

• package.json: 1.1.6 → 1.1.7.
• package-lock.json: the two project-level version fields only, so no dependency entry moves.
• CHANGELOG.md: a v1.1.7 entry.

After merge

1. Tag v1.1.7 on the merge commit. publish-dashboard-bundle.yml attaches the bundle and its sha256.
2. omnimarket pins it.

Evidence-Source: OCC#13370
Evidence-Ticket: OMN-20753

🤖 Generated with Claude Code

[onexbot-occ-writer]

OCC autobind did not mint a companion for this PR: no changed-file candidate could be proven RED against the merge base, and emitting a PR-existence probe instead would be non-falsifiable evidence (OMN-15247). Hand-authored evidence is required.

Considered 3 changed file(s):

• CHANGELOG.md: release-line source, but the diff also changes a path that is not a release artefact, so release lines are not offered
• package-lock.json: no candidate grammar reads this file type (only Python declarations, uv.lock lines, release-artefact lines and contract-pin lines are proposed)
• package.json: no candidate grammar reads this file type (only Python declarations, uv.lock lines, release-artefact lines and contract-pin lines are proposed)

This verdict is occ-autobind's, derived from this head and its merge base alone. A second producer, the occ-companion-effect backstop, consumes its own command on the lab bus and may still mint a companion under the generic binding. Whether it does depends on that consumer running, not on this diff (OMN-18876).