[063] Prepare source publication and release readiness

[konard]

Summary

• Adds a machine-readable release readiness checklist covering tests, license and source publication review, privacy review, security audit evidence, release artifacts, documentation completeness, and explicit human release approval.
• Adds docs/release-readiness.md with the final release gate checklist plus a current behavior inventory that maps foundation behavior to source, tests, and documentation.
• Wires the readiness gate into npm run validate:release, npm run validate:foundation, and regression coverage in test/release-readiness.test.mjs.
• Links the release readiness document from README, BUILD-GUIDE, CONTRIBUTING, and release strategy docs, and removes the generated placeholder .gitkeep.

Issue

Fixes #29

Reproduction / Verification

Before this work, node --test test/release-readiness.test.mjs failed because there was no release readiness module, no docs/release-readiness.md, and no release validation hook enforcing the final publication gate. The new test now verifies the checklist order, required human approver roles, source publication and documentation completeness language, documentation inventory coverage, and validate:release enforcement.

Tests

• node --test test/release-readiness.test.mjs
• npm test
• npm run validate:secrets
• npm run audit:security
• npm run validate:foundation
• npm run validate:release
• npm run build:debug-artifacts
• npm run decompose:dry-run
• git diff --check --cached

Risk

This is release documentation and validation only. It does not publish packages, add signing secrets, or change runtime behavior. Public release still requires a human release approver after the checklist is complete.

Screenshots or recordings

Not applicable. This is release documentation and validation with no rendered UI.

Security and privacy

• This PR does not include secrets, production credentials, access tokens, Telegram API hashes, private keys, or private message content.
• Any logs, screenshots, or fixtures are redacted.
• Security-sensitive release readiness changes request human maintainer review before release.

[konard]

Solution summary

Implemented and pushed the fix for issue #29.

PR: #134

What changed:

• Added docs/release-readiness.md with the final release checklist, source publication requirements, documentation completeness rules, and human release approval gate.
• Added src/foundation/release-readiness.mjs plus test/release-readiness.test.mjs.
• Wired the readiness gate into npm run validate:release and npm run validate:foundation.
• Updated README, BUILD-GUIDE, CONTRIBUTING, and release strategy docs.
• Removed the placeholder .gitkeep.
• Updated PR title/body and marked PR 134 ready for review.

Verification:

• npm test
• npm run validate:secrets
• npm run audit:security
• npm run validate:foundation
• npm run validate:release
• npm run build:debug-artifacts
• npm run decompose:dry-run
• git diff --check --cached

CI is passing on head commit 359a7689f6d463e3519209bde08ba570f1f262b0, and the working tree is clean.

---

This summary was automatically extracted from the AI working session output.

[konard]

🤖 Solution Draft Log

This log file contains the complete execution trace of the AI solution draft process.

💰 Cost estimation:

• Model: GPT-5.5
• Provider: OpenAI
• Public pricing estimate: $7.880125

📊 Context and tokens usage:

• 5.2M / 1.1M (499%) input tokens, 26.5K / 128K (21%) output tokens

Total: (160.5K + 5.1M cached) input tokens, 26.5K output tokens, $7.880125 cost

🤖 Models used:

• Tool: OpenAI Codex
• Requested: gpt-5.5
• Model: GPT-5.5 (gpt-5.5)

📎 Log file uploaded as Repository (35977KB)

• View complete solution draft log

---

Now working session is ended, feel free to review and add any feedback on the solution draft.

[konard]

✅ Ready to merge

This pull request is now ready to be merged:

• All CI checks have passed
• No merge conflicts
• No pending changes

---

Monitored by hive-mind with --auto-restart-until-mergeable flag