Skip to content

Prepare ID 0.5.2 hardening release - #4

Merged
markoblogo merged 1 commit into
mainfrom
codex/v0.5.2-hardening
Sep 11, 2026
Merged

markoblogo merged 1 commit into
mainfrom
codex/v0.5.2-hardening

Conversation

@markoblogo

Copy link
Copy Markdown
Owner

ID 0.5.1 documented stale companion versions and exposed registry files for an MCP server the package does not run. This prepares 0.5.2 with an honest adapter boundary, current SET compatibility, a smaller context handshake, and an installed-user path that can be reproduced from the wheel.

What changed

  • verify Python 3.11–3.14 and pin agentsgen 0.5.0 / SET 0.4.0 across CI, release, docs, and demos
  • remove obsolete MCP registry publication scripts and manifest; retain a design-only adapter contract and resource export
  • replace mandatory 5–10 bullet handshakes with task-relevant context loading and blocker-only questions
  • fix the stale versioned integration-guide URL and expose the packaged redactor as idctl redact
  • rewrite README, quickstart, privacy, ecosystem, integration, and contributor docs; add SECURITY.md, AGENTS.md, and Dependabot
  • refresh repository About, homepage, topics, Dependabot security updates, and private vulnerability reporting

Validation

  • make validate — 53 tests pass; generated artifacts validate
  • make drift-check — clean
  • make coverage — 78%
  • wheel and sdist build; twine check passes
  • clean wheel install passes all three synthetic demos with ID 0.5.2, agentsgen 0.5.0, and SET 0.4.0
  • Markdown local links and workflow YAML validate

The checked-in owner profile remains unchanged. Validation reports its existing stale review dates; this release does not renew them without a content review.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 11, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-09-11T15:52:45.433558Z cab282a PR opened
ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@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: cab282a7dc

ℹ️ 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".

Comment thread README.md
Legacy list policies from earlier releases are normalized in memory during validation and export. Their source files remain unchanged and their restrictions remain effective. `--allow-unfiltered` only permits a missing policy in a reviewed legacy workflow; it cannot bypass an invalid policy.

Generating or exporting a file does not upload it. Source profiles remain under your control.
Review the resulting export before attaching it to another tool. See the [privacy model](docs/PRIVACY.md), [policy schema](docs/PRIVACY_POLICY_V1.md), and [threat model](docs/THREAT_MODEL.md).

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Restore the unfiltered-export warning

When users follow the Share path in docs/QUICKSTART.md, they validate a privacy policy and then create interop.v1.json, but scripts/export_interop_v1.py never loads that policy and therefore includes fields marked local_only or left unlisted. This rewrite removes the previous explicit warning that interop and soul artifacts are not privacy-filtered, so readers may treat policy validation as protecting those artifacts; explicitly limit this review guidance to compact/MCP output and restore the warning for unfiltered artifacts.

AGENTS.md reference: AGENTS.md:L14-L14

Useful? React with 👍 / 👎.

Comment thread README.md
idctl export-interop --owner-id demo
idctl export-compact --owner-id demo
idctl validate-compact --owner-id demo
idctl diff --owner-id demo --since 7d

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 Initialize Git before running the diff

In the documented fresh-directory flow, no Git repository or baseline commit is created before this command. idctl diff --since 7d requires Git history and exits with status 2 (no git revision found before ...), so the advertised five-minute sequence ends in an error for a new user; initialize and commit a baseline first, or move this command to an optional Git-backed workflow.

AGENTS.md reference: AGENTS.md:L7-L7

Useful? React with 👍 / 👎.

Comment thread README.md
Requires Python 3.11 or newer.

```sh
uv tool install id-protocol

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 Declare or avoid the uv prerequisite

The preceding requirement now says only Python 3.11+ is needed, but the first installation command invokes the separate uv executable. On a normal Python installation without uv, the quickstart fails immediately with uv: command not found; either retain uv as an explicit prerequisite with installation guidance or provide a pip/pipx command.

Useful? React with 👍 / 👎.

@markoblogo
markoblogo merged commit e1ee71b into main Sep 11, 2026
5 checks passed
@markoblogo
markoblogo deleted the codex/v0.5.2-hardening branch September 11, 2026 16:13
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