Skip to content

Godpowers 5.5.0: Arc Ready and Pillars 1.1#70

Merged
hannsxpeter merged 1 commit into
mainfrom
codex/arc-pillars-1-1-hardening
Jul 13, 2026
Merged

Godpowers 5.5.0: Arc Ready and Pillars 1.1#70
hannsxpeter merged 1 commit into
mainfrom
codex/arc-pillars-1-1-hardening

Conversation

@hannsxpeter

Copy link
Copy Markdown
Owner

Summary

  • Add six-form product routing and four-axis domain composition.
  • Add OWASP 2025 hardening and a hash-bound prepublication gate.
  • Add Arc-Ready import and managed sync-back support.
  • Implement Pillars 1.1 routing, scope, catalog, budget, and conformance behavior.
  • Separate project Pillars context from portable specialist source contracts.
  • Update the complete documentation and release surface to 5.5.0.

Verification

  • Complete test suite passed.
  • Release gate passed with 94.64 percent line coverage and 79.26 percent branch coverage.
  • Official Agent Skills validation passed.
  • Official Pillars validation passed with 0 errors and 0 warnings.
  • Self-project truth passed 141 checks.
  • Root and MCP package checks passed for 582 and 8 files.
  • Prepublication gate passed with 0 unresolved or accepted Critical findings.

@hannsxpeter hannsxpeter merged commit 84fbd00 into main Jul 13, 2026
4 checks passed
@hannsxpeter hannsxpeter deleted the codex/arc-pillars-1-1-hardening branch July 13, 2026 16:05

@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: 8aa291aa5f

ℹ️ 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 +105 to +107
if (current.hardeningStatus !== 'done') reasons.push(`hardening status is ${current.hardeningStatus || 'missing'}, expected done`);
if (current.explicitBlocked) reasons.push('hardening findings record a blocked launch gate');
if (current.criticals.unresolved > 0) reasons.push(`${current.criticals.unresolved} unresolved or accepted Critical finding(s)`);

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 Require hardening timestamps before passing the gate

When state.json has tier-3.harden.status = done but the updated field is missing or not parseable, snapshot() sets hardeningUpdatedAt to null and this evaluation adds no blocker, so record() can write a passing PREPUBLICATION gate that is not bound to an authoritative hardening timestamp. Since this gate is meant to invalidate after hardening state changes, it should fail closed unless updated is a valid date.

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