Skip to content

fix: AIOS v0.6.1 conformance suite alignment (0.4.5) - #50

Merged
pramodbn27 merged 7 commits into
mainfrom
fix/aios-0.6.1-suite-alignment
Oct 31, 2026
Merged

pramodbn27 merged 7 commits into
mainfrom
fix/aios-0.6.1-suite-alignment

Conversation

@pramodbn27

Copy link
Copy Markdown
Member

Summary

Running the new AIOS v0.6.1 portable conformance suite (DeepAgentLabs/ai-operations-spec#36) through spec.validate_artifact exposed two 0.4-draft divergences:

  • A Step whose ended_at precedes started_at passed; it now fails AIOS-0.4-P04 like the Run-level check.
  • An artifact type the declared marker does not publish (e.g. a provenance record labeled 0.4-draft) returned an accept compatibility decision beside the error; it is now rejected under AIOS-0.5-V03.

Adds tests/test_spec_conformance_suite.py, which runs the suite from the sibling checkout (skips until the spec PR merges): all 0.4-draft cases match expected outcomes and rule citations; 0.6-draft provenance cases are rejected under V03.

Docs: docs/aios-0.6.1.md (+ mkdocs nav), README, ROADMAP, CHANGELOG 0.4.5; version bump. No dependency or hosted pin changes.

Test plan

  • uv run pytest (294 passed locally against the spec branch), ruff, mypy, mkdocs --strict

…types under V03

The AIOS v0.6.1 conformance suite showed that a Step ending before it
started passed validation (AIOS-0.4-P04), and that an artifact type the
declared marker does not publish (for example a provenance record under
0.4-draft) was rejected without the AIOS-0.5-V03 routing decision.
…checkout

Cases for markers this server checks must match the expected outcome and
rule citations; 0.6-draft provenance cases must be rejected under
AIOS-0.5-V03. Skips when the suite is not checked out.
Copilot AI lite review requested due to automatic review settings October 31, 2026 11:49
@pramodbn27
pramodbn27 requested a review from a team as a code owner October 31, 2026 11:49
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 31, 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-10-31T11:51:14.611208Z a772c1a 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: a772c1a7e5

ℹ️ 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 on lines +491 to +492
step_started = datetime.fromisoformat(step["started_at"].replace("Z", "+00:00"))
step_ended = datetime.fromisoformat(step["ended_at"].replace("Z", "+00:00"))

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 Normalize lowercase UTC markers before parsing Step timestamps

For a Run with ordinary uppercase-Z timestamps but a Step timestamp such as 2026-10-31T12:00:00z, the new semantic check raises ValueError instead of returning a validation result. Lowercase z is valid in RFC 3339 and passes the configured FormatChecker, but datetime.fromisoformat() rejects it because this replacement only handles uppercase Z. Normalize both forms before parsing Step timestamps so otherwise valid artifacts do not fail validation with an exception.

Useful? React with 👍 / 👎.

Copilot AI 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.

🟢 Approval recommended

No active review issues are recorded, and the change addresses the conformance, compatibility, coverage, documentation, and release-metadata updates described in the review.

No open issues 🎉

What changed in this PR

This pull request aligns AIOS artifact validation with the v0.6.1 conformance expectations and releases version 0.4.5.

Changes:

  • Adds AIOS-0.4-P04 validation for invalid Step timestamp ordering.
  • Rejects unsupported artifact types under AIOS-0.5-V03.
  • Adds portable conformance-suite coverage.
  • Updates AIOS documentation, navigation, roadmap, changelog, and version metadata.

This pull request requires changes.

File Description
uv.lock Updates the locked package version to 0.4.5.
tests/​test_spec_conformance_suite.py Runs AIOS v0.6.1 conformance cases when the sibling checkout is available.
src/​deep_agentic_core_mcp/​adapters/​ai_operations_spec.py Adds artifact-type compatibility rejection and Step timestamp validation.
src/​deep_agentic_core_mcp/​__init__.py Bumps the runtime package version to 0.4.5.
server.json Updates MCP registry and package metadata versions.
ROADMAP.md Records AIOS v0.6.1 conformance and compatibility status.
README.md Documents the updated AIOS compatibility behavior.
pyproject.toml Bumps the project version to 0.4.5.
mkdocs.yml Adds the AIOS 0.6.1 documentation page to navigation.
docs/​aios-0.6.1.md Documents supported, unchecked, and rejected AIOS markers.
CHANGELOG.md Adds the 0.4.5 release notes.

Review effort: Lite

@pramodbn27
pramodbn27 merged commit e5f5eb1 into main Oct 31, 2026
13 checks passed
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.

2 participants