security: enforce the approved keyframe repository and package boundary

[WalksWithASwagger]

Summary

Enforce the human-approved repository and npm-package boundary for keyframe configuration files.

Context

• Blocked by security: protect local environment-file variants from tracking #317 and decision(security): classify tracked keyframe configs before public release #322.
• Roadmap phase: Phase 1 - public release hygiene
• Relevant files: .gitignore, package.json, scripts/check-package-boundary.mjs, scripts/check-public-boundary.py, tests/test_public_boundary.py, docs/FLOYO.md, and only the keyframe paths approved in decision(security): classify tracked keyframe configs before public release #322
• Current behavior: tracked config/keyframes*.json files are described as private by ignore policy yet included by a broad npm-package wildcard.
• Desired behavior: only exact, human-approved public fixtures can be tracked or packaged.

Implementation Notes

• Treat the classifications recorded in decision(security): classify tracked keyframe configs before public release #322 as authoritative without reproducing file contents in GitHub.
• Land security: protect local environment-file variants from tracking #317 first because both issues change the public-boundary checker and tests.
• Replace broad keyframe wildcards with explicit approved paths.
• Stop rather than rewriting history if decision(security): classify tracked keyframe configs before public release #322 identifies material that requires private remediation.

Acceptance Criteria

• Files classified private in decision(security): classify tracked keyframe configs before public release #322 are absent from the tracked tree and npm tarball.
• Any approved replacement is a sanitized public template with an unambiguous filename.
• package.json contains no broad config/keyframes*.json package wildcard.
• Package checking fails when an unapproved keyframe config enters the tarball.
• Public-boundary checking rejects tracked private keyframe configuration.
• .gitignore, package policy, and FLOYO documentation describe the same boundary.
• No keyframe contents are printed into CI logs or PR discussion.

Tests/Evals

• Extend public- and package-boundary regression fixtures using synthetic filenames and content only.
• Preserve existing keyframe job behavior tests.

Verification

• python3 -m pytest tests/test_public_boundary.py tests/test_keyframe_jobs.py -q
• npm run public:check
• npm run pack:check
• npm pack --dry-run --json
• git ls-files 'config/keyframes*'
• npm test

Agent Instructions

• Use branch codex/issue-<this-issue>-keyframe-boundary.
• Do not start until security: protect local environment-file variants from tracking #317 is merged and decision(security): classify tracked keyframe configs before public release #322 records all classifications.
• Do not paste, transform, or summarize private values.
• Implement only the disposition authorized in decision(security): classify tracked keyframe configs before public release #322.

Human Checkpoints

• Stop if decision(security): classify tracked keyframe configs before public release #322 calls for history review, privacy disclosure, or a disposition not expressible as an ordinary forward commit.

Out of Scope

• Git history rewriting.
• Credential rotation, provider calls, npm publishing, or generated outputs.
• Changing keyframe generation behavior.

Linear

Not applicable. Rafiki delivery is GitHub-only; do not create or update a Linear issue.

[WalksWithASwagger]

Unblocked — #322 decided, #317 closed

Both blockers are cleared: #317 is merged, and #322 classified all four config/keyframes*.json files as approved public fixtures (GitHub + npm). No keyframe files are removed or privatized.

Scope (reframed for the all-public decision)

1. Package boundary: replace the broad config/keyframes*.json entry in package.json files[] with the four explicit approved paths (config/keyframes.json, config/keyframes-kevin.json, config/keyframes-mage.json, config/keyframes-mayumi.json).
2. Reconcile the boundary docs/policy: .gitignore:90-91 currently labels these "Private likeness config … not for the public tool repo," which now contradicts the decision. Update the comment to reflect public-fixture status; decide whether to keep the config/keyframes*.json ignore pattern as a default-private guard for new keyframe files (the four tracked ones stay tracked regardless). Align docs/FLOYO.md to the same boundary.
3. Tests: extend tests/test_public_boundary.py / package-boundary checks (synthetic filenames + content only) so an unapproved keyframe file is rejected from tree/tarball while the four approved fixtures pass. Preserve existing keyframe job behavior tests.

Out of scope

• Do NOT remove, untrack, or rewrite history for any keyframe file.
• Do NOT publish, tag, or change package identity (that's package: adopt the scoped npm identity without publishing #332/release: approve and publish the first verified scoped npm release #334).

Verification (from the issue)

python3 -m pytest tests/test_public_boundary.py tests/test_keyframe_jobs.py -q · npm run public:check · npm run pack:check · npm pack --dry-run --json · git ls-files 'config/keyframes*' · npm test

[github-actions]

Agentic dev loop started on branch codex/issue-323-security-enforce-the-approved-keyframe-repositor with provider noop.