docs(changelog): log advisory gate release

[JasonColapietro]

What changed

• add the missing 33ebb14 advisory-gates release to the GitHub Pages homepage ship log
• keep the existing aeaa416 opaque-public-policy entry and place both releases in real commit order
• preserve the existing timeline markup, filter type, date format, and direct GitHub commit links

Why

The homepage already recorded aeaa416, but it did not reflect the later merged release that made claim and verification gates advisory instead of blocking.

Verification

• node scripts/validate-skill-pack.mjs --strict — 67/67 skills
• npm run ci — validator runtime 12/12, MCP 11/11, trigger routing 27/27, Python 23/23
• npm run audit:dependencies — 0 vulnerabilities
• git diff --check
• rendered docs/index.html at 1440×1000 and 390×844; both hashes display cleanly and the Fixes filter retains both entries

[JasonColapietro]

Rebased onto the new origin — content is fine, CI cannot report

This branch is now up to date with main (which includes the skills.suedeai.ai migration, #60). The feared conflict never materialised: the changelog <li> this PR adds sits far from anything the migration touched, and the two merged cleanly with zero conflicts.

I ran the full suite locally against this PR's merged head (2a59e91):

npm run ci  →  exit 0, 29 tests, "Validated 71 skills against 71 catalog entries"

This is not merged, and the reason is not this PR. GitHub Actions has stopped firing pull_request and push events for this repository. gh pr checks reports "no checks reported", so the required build and validate checks cannot report and mergeStateStatus is BLOCKED. Retriggering via close/reopen and via a synchronize (empty commit, since reverted) both produced no run.

Merging would require an admin bypass of required checks — the exact failure mode the build job in skill-pack-ci.yml was added to end — so I have deliberately left it alone. Once Actions recovers, a fresh push here should go green and it can merge normally.