docs: close out the 1.1.6 changelog heading

[trial-roe]

Why

CHANGELOG.md still files the skip_cache feature under ## Unreleased, but it shipped in 1.1.6 — verified against the tags: git show v1.1.5:src/roe/api/agents.py | grep -c skip_cache → 0, and the same command at v1.1.6 → 17.

This is not a one-off oversight. The release fan-out never touches this file by design — roe-sdk/src/roe_sdk/prepare_target.py: "CHANGELOG.md is intentionally not touched (historical record)". So no release PR has ever closed the heading out, and none will. Left alone, 1.1.7 ships with an empty changelog too.

The only open PR that touches CHANGELOG.md is #66, which closes the heading out as 1.2.0 — the wrong version (1.2.0 was a roe-golang-only bump, and this repo's live line is 1.1.x continuing to 1.1.7 in #69). #66 should be closed rather than merged: its reason to exist was deleted upstream by roe-main 3ae83b888 ("Version SDK release targets independently", #3747), which removed the cross-repo version lockstep guard. This PR salvages the one genuinely useful line from it, at the correct version.

What

One line: ## Unreleased → ## 1.1.6.

No version file changes, so tag-on-release-merge.yml does not fire and nothing publishes.

The same fix is up for roe-typescript, whose CHANGELOG.md has the identical stale heading over its skipCache entry.

🤖 Generated with Claude Code

[greptile-apps]

Greptile Summary

This update moves the existing skip_cache release notes from the unreleased section into version 1.1.6.

The checked release metadata and tag context match the new heading, the feature notes remain in place, and the resulting changelog structure is valid.

Confidence Score: 5/5

T-Rex Logs

What T-Rex did

• I ran the changelog heading validator against the base commit 435bcb5 and confirmed the Markdown structure check passed.
• I ran the same validator at HEAD, where the heading sits under 1.1.6, and it matched the project version and v1.1.6 tag, retained the skip_cache=True notes, and passed the Markdown structure check.
• I captured the exact validator source and verified the before and after states, showing that before output the base had Unreleased with skip_cache=True and structurally valid, and after output HEAD had 1.1.6, matched the version and tag, retained skip_cache=True, and remained structurally valid.

_{Ran code and verified through T-Rex}

_{Reviews (1): Last reviewed commit: "docs: close out the 1.1.6 changelog head..." | Re-trigger Greptile}

[trial-roe]

Added the stale-fixture commit here as well (cherry-pick of 24df7a6, the same commit on #69's branch) so this PR is green on its own instead of inheriting main's red test job.

Context: main has been failing these four tests since #68 merged on 2026-07-29 (run 30493974267) — KeyError: 'dynamic_inputs' / 'updated_at', from hand-written response fixtures that never picked up newly-required serializer fields. Any PR branched off main inherits it, including a one-line changelog edit.

The commit is byte-identical on both branches, so either merge order is fine — whichever lands second is a no-op for those two files. Merging this one also un-reds main immediately, without waiting on the 1.1.7 release.