Skip to content

πŸ“‹ v1.11 review umbrella follow-ups β€” codex P2/P3 from PR #81~#94Β #95

Description

@sgwannabe

Context

13 issues (#58~#79 in-scope subset) were closed via PRs #81~#94 in waves W1-W4. Each PR ran codex review with the policy: apply only P1 before push, defer P2/P3 to follow-up. This umbrella tracks those deferred items so they don't decay in PR description archaeology.

Convention

  • All items here are non-blocking (the parent PR shipped without them).
  • Each line: [Source PR] <topic> β€” <one-line rationale>.
  • Open a single follow-up PR per cluster (don't reopen 16 PRs); group by file or theme.

Items

Layered enforcement / defense in depth (S-3 / I-3 follow-up)

Security (factory-policy / regex)

Lint / fixture polish

Suggested clustering for follow-up PRs

Cluster Items Files
Defense in depth (input/read-path caps) #83Γ—2 commands/new.md, cache replay loader
Security regex polish #85Γ—2 factory-policy.py, url-injection-positives.json
Fixture asserts strengthening #87, #88, #89, #91, #93 various tests/fixtures/
Workspace + locale hardening #92Γ—2 mock-bootstrap.sh, generate-gallery.sh
Dev tooling pinning #94 new requirements.txt or pyproject.toml
Wording fixes #82, #89 docs

Status

  • Defense in depth cluster
  • Security regex polish
  • Fixture strengthening
  • Workspace hardening
  • Dev tooling pinning
  • Wording fixes

References

Metadata

Metadata

Assignees

No one assigned

    Labels

    follow-upCodex/review follow-up items extracted from prior PRsv1.12-backlogDeferred to v1.12+ (post-v1.12 hardening backlog)

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions