[Wave 2] Add verified client release and compliance Skill evidence #10

Merged

lprintf merged 2 commits from w2/printf-prototype into main

2026-07-23 00:34:18 +08:00

lprintf commented

2026-07-23 00:33:53 +08:00

Owner

What changed

record fixed, publicly verifiable Native and Docker client release evidence
document the default Compose Bridge topology and minimal application-entry exposure
link the public printf-client-release Agent Skill, task entry, and OpenAI metadata
summarize Skill constraints for authentication preservation, token secrecy, idempotent Mapping, fail-fast errors, and final HTTPS verification
keep the enterprise Skill separate from the four Printf Wave 2 core SaaS Skills
document material limits: privileged/NET_ADMIN, broad bearer token scope, protocol v0, and unsigned packages

Why

The enterprise client repository now provides executable Compose and compliance-oriented Agent workflows rather than only release documentation. Referencing fixed evidence improves engineering verifiability without changing the competition prototype scope.

Validation

fixed GitHub commits, Release, Compose files, Skill files, OpenAI metadata, and successful CI verified through authenticated GitHub API
all relative Markdown links resolve
git diff --check and secret-pattern checks pass

## What changed - record fixed, publicly verifiable Native and Docker client release evidence - document the default Compose Bridge topology and minimal application-entry exposure - link the public `printf-client-release` Agent Skill, task entry, and OpenAI metadata - summarize Skill constraints for authentication preservation, token secrecy, idempotent Mapping, fail-fast errors, and final HTTPS verification - keep the enterprise Skill separate from the four Printf Wave 2 core SaaS Skills - document material limits: privileged/NET_ADMIN, broad bearer token scope, protocol v0, and unsigned packages ## Why The enterprise client repository now provides executable Compose and compliance-oriented Agent workflows rather than only release documentation. Referencing fixed evidence improves engineering verifiability without changing the competition prototype scope. ## Validation - fixed GitHub commits, Release, Compose files, Skill files, OpenAI metadata, and successful CI verified through authenticated GitHub API - all relative Markdown links resolve - git diff --check and secret-pattern checks pass

lprintf added 2 commits

2026-07-23 00:33:53 +08:00