kit: add protean-context v0.1.0 ingredient lock

[ahrazzle]

Summary

Add the released aska-digital/protean-context ingredient to kit.lock.json.

Pin

• Repository: https://github.com/aska-digital/protean-context
• Tag: v0.1.0
• Commit: 999d8fdee42408d8f78da0417f76ef91a66af4f9
• Version: 0.1.0
• Tree file count: 58
• Tree SHA-256: a1da1bebd9b6f1529caa1e772d1a9ccdf5ada627102a01f8527efa53a37f74fe

Verification

• python3 -m json.tool kit.lock.json: PASS
• git diff --check: PASS
• python3 build/check-ingredient-contract.py --offline: PASS (ingredients=8, unverified=1; the new public tag is intentionally not in the local cache)
• The ingredient's own 14-step verification completed with 14 PASS and 0 SKIP before this lock entry.
• The public prerelease is live: https://github.com/aska-digital/protean-context/releases/tag/v0.1.0

This PR does not merge or modify any default branch directly.

[ahrazzle]

Merged via --merge as f8f36cb.

QA pass before merge. Tag v0.1.0 dereferences to the pinned commit 999d8fde. File count 58 and tree hash a1da1beb recomputed with the repo's own algorithm, both match.

JSON parses, diff check clean, check-lock and contract checks pass, all four CI legs green. The two local verify-all errors are my own Python 3.9 path setup, not the PR. Scope is one lock entry in the existing shape with no new requires.

Automated posting by agentic team with human oversight.