Skip to content

Modernize the public Codex field guide - #4

Merged
jremick merged 1 commit into
mainfrom
codex/public-alpha-refresh
Aug 19, 2026
Merged

Modernize the public Codex field guide#4
jremick merged 1 commit into
mainfrom
codex/public-alpha-refresh

Conversation

@jremick

@jremick jremick commented Aug 19, 2026

Copy link
Copy Markdown
Owner

Summary

  • modernize the guide around current Codex tasks, skills, plugins, MCP, delegation, environments, browser/computer use, artifacts, goals, schedules, models, permissions, rules, and hooks
  • replace "Thinking Altitude" with "Thinking Abstraction Level" and use synthetic, generalized public examples
  • add dated official-source boundaries and explicit public-alpha, support, security, and no-release language
  • harden content validation, reviewed-asset hashes, and the GitHub Actions trust boundary

Security and privacy

  • removes personal attribution, project-specific examples, machine paths, account URLs, and environment inventories from public content
  • rejects common credentials, local paths, private IPs, raw identifier shapes, unreviewed source hosts, unsafe SVG features, unreviewed asset changes, and repository symlinks
  • grants the workflow only contents: read, disables persisted checkout credentials, uses a bounded runner and timeout, and pins actions to reviewed commit SHAs
  • does not rewrite historical commits; existing publisher and hosting metadata remain outside this change

Validation

  • python3 -m unittest discover -s tests -v
  • python3 scripts/validate_content.py
  • python3 -m py_compile scripts/validate_content.py tests/test_validate_content.py
  • workflow YAML parse
  • git diff --check
  • asset hash, dimensions, metadata, privacy-string, identity, and retired-phrase checks
  • live tag-to-SHA verification for actions/checkout v7 and actions/setup-python v7

Release boundary

This publishes a public-alpha documentation update only. It does not create a release, change repository settings, apply the custom social preview, or claim beta/stable maturity.

@jremick
jremick merged commit f985412 into main Aug 19, 2026
2 checks passed
@jremick
jremick deleted the codex/public-alpha-refresh branch August 19, 2026 21:41

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 354e1c0fa7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

if not isinstance(value, str):
return False
try:
return date.fromisoformat(value).isoformat() == value

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Reject future review dates

When a contributor supplies a future value such as 9999-12-31, this helper returns true and the catalog, asset-manifest, and product-source checks all accept it. The problem is already visible in this commit: the catalog, manifest, README, and product guides claim updates or reviews on 2026-08-20, while the commit was authored and committed on 2026-08-19 UTC. Compare parsed dates with the current date so CI cannot certify reviews or updates that have not yet occurred.

Useful? React with 👍 / 👎.

"script content": r"<script\b",
"event-handler attribute": r"\son[a-z]+\s*=",
"active or embedded href": r"(?:href|xlink:href)\s*=\s*['\"]\s*(?:javascript:|data:)",
"external href": r"(?:href|xlink:href)\s*=\s*['\"]\s*https?://",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Reject scheme-relative SVG references

When an SVG contains a scheme-relative reference such as <image href="//tracker.example/pixel">, this expression does not match it, and URL_PATTERN also misses it because that pattern requires http:// or https://. A browser can resolve and request that external resource when the asset is rendered, so such an SVG passes the new metadata/privacy gate despite retaining an external dependency; reject // and other externally resolving href forms as well.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant