chore: refresh skills-lock.json hashes after skills install

[PsiACE]

Which issue or RFC does this PR close?

N/A — routine maintenance following make skills-install.

Rationale for this change

npx skills experimental_install recomputed the content hashes for two pinned skills (humanizer, kill-ai-slop) while installing them into .agents/skills/. The lock file should reflect the hashes of the skill content actually installed so future installs are reproducible and idempotent.

What changes are included in this PR?

• Update computedHash for humanizer and kill-ai-slop in skills-lock.json to match the freshly installed skill content.
• No code, docs, or test changes.

Are there any user-facing changes?

No.

How was this change tested?

• npx skills experimental_install completed: all 5 pinned skills installed under .agents/skills/.
• npx skills verify (or equivalent) reported OK for all 5 skills.
• git status clean after commit; .agents/skills/ is gitignored and restored from the lock file.

AI usage statement

Used GitHub Copilot/Codex-style agent assistance to run the install command, verify results, and prepare this PR description.

[Copilot]

Pull request overview

This PR updates skills-lock.json to keep the lockfile in sync with the hashes produced by npx skills experimental_install, ensuring pinned agent skill installs remain reproducible and idempotent.

Changes:

• Updated computedHash for the humanizer skill to match the freshly installed content.
• Updated computedHash for the kill-ai-slop skill to match the freshly installed content.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[PsiACE]

Verification summary:

• Worktree synced to origin/master (ee2e543, PR docs: point Git install references to master #1206 merged).
• npx skills experimental_install installed all 5 pinned skills into .agents/skills/ (gitignored, restored from the lock file): documentation-writer, friendly-python, humanizer, kill-ai-slop, piglet — each verified OK.
• The installer recomputed computedHash for humanizer and kill-ai-slop; this PR commits those refreshed hashes so future installs stay idempotent.
• CI: Main (quality/tests 3.11–3.14/check-docs), Build customer artifact, and E2E harness all pass. Acceptance (oceanbase) passed on rerun; the initial failure was a flaky harness container exit (exit 3) unrelated to this diff.