fix: lead first use with AI profiles and a real Demo - #46
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
EvoZeus Privacy ScanMode: dry-run Findings
Next action
|
EvoZeus Queue GuardMode: dry-run Author open PRs: 6 Branch family: codex/bug/20260731-skill-positioning-demo Branch family open PRs: 1 Violations
Next action
|
EvoZeus Labeler ReportPR type/risk labels were updated from changed files. Surfaces
Labels
Changed lines
|
EvoZeus Dirty PR CheckMode: dry-run Surfaces
Reasons
Next action
|
EvoZeus Proof GateMode: dry-run Proof labels
Missing or weak fields
Next action
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6e2de4f4e7
ℹ️ 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".
EvoZeus Auto ResponseMissing real behavior proofThis PR needs real behavior proof before review can continue. Add the command, environment, input, output after the patch, observed result, and what was not tested. Split this PRThis PR appears to mix too many surfaces or protected paths. Split it into one primary layer and one review target. Owner review requiredThis PR changes a protected path. CODEOWNERS review and maintainer approval are required; do not request automerge. Queue limit reachedThis author or branch family appears to exceed the current queue limit. Reduce open PRs or ask a maintainer to override before continuing review. |
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8bbe6fdf72
ℹ️ 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".
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ff0756b6fa
ℹ️ 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".
|
@codex review Please review exact head |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3f58f2c87c
ℹ️ 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".
|
@codex review Please review exact head |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b213b8d81a
ℹ️ 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".
|
@codex review Please review exact head |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f08a61bbf0
ℹ️ 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".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 7ec3db7c82
ℹ️ 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".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 37003a59fa
ℹ️ 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".
|
Codex Review: Didn't find any major issues. Bravo. Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
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". |
Summary
Lead first-time EvoZeus users to its two primary outcomes, enforce one explicitly approved Codex history path end to end, and replace the obsolete README Demo with a contract-accurate managed Skillware example.
Linked Context
Addresses #43
Addresses #45
#45remains open because its acceptance requires a real Stable Release that contains the Harness. The Demo repository's current Stablev0.1.0predates Harness attachment; a later Demo Release and full Stable-Harness smoke are still required.PR Scope
Instruction surface changed
The Codex and Claude plugin metadata, generated host marketplace description,
features --json, installed onboarding template,skills/using-evozeus, and both root READMEs now lead with two primary outcomes:Session review, Lesson capture, feature discovery, Stable/UAT, Doctor, update, and rollback remain supporting routes.
Why this change is needed
The installed Plugin page previously framed EvoZeus around Session review, Lesson capture, and version maintenance. The root READMEs also linked an obsolete Demo and promised a large scenario map that the real Demo Skill does not produce. First-time users could not identify the current primary value or trust the Demo contract.
Agent behavior before / after
Before:
Enterprise-ai-scenario-map-skilland claimed a large scenario inventory.After:
features --jsonexposes these two entries first withproduct_tier: primary, while all supporting entries remain discoverable;MetaInFLow/diagnose-enterprise-ai-scenarios, its Stable business contract, and the currentmainHarness manifest as separate facts.Safety boundary
Prompt injection risk
The external Demo repository was treated only as evidence at pinned refs. Its content did not grant write, release, or publication authority. The smoke used the explicit user-approved sample prompt, read-only sandboxing, and an ephemeral Codex session.
EvoZeus Evidence Proof
npm test;npm run test:python;claude plugin validate .;python3 -m py_compile scripts/check_pr_ready.py;python3 scripts/check_pr_ready.py --base origin/main;python3 scripts/check_pr_ready.py --base origin/main --allow-cross-layer;git diff --check; isolatedcodex exec --ephemeral --sandbox read-onlywith the documented Demo prompt.scan_sessionsunchanged, and the Stable Demo returned three candidate rows, one recommended scenario, and quantitative pass conditions.v0.1.0predates Harness attachment, so Stable-Harness end-to-end evidence requires a later Demo Release; the exact no-flag readiness command reports the intentional cross-layer scope.Tests and Validation
npm test— passed: 83 Node tests plus GitHub gate tests.npm run test:python— passed: Session Signal 97 passed, 2 skipped, 18 subtests; Runtime 94 passed, 4 skipped.claude plugin validate .— passed.python3 -m py_compile scripts/check_pr_ready.py— passed.python3 scripts/check_pr_ready.py --base origin/main— reports the intentional Governance/Execution/Semantic scope required by this one product-narrative PR.python3 scripts/check_pr_ready.py --base origin/main --allow-cross-layer— passed.git diff --check— passed.Live Demo evidence:
v0.1.0, tag Commit4174f9077b6f5bb678e08e57e3cf32b0a1f1122d.SKILL.mdrequires exactly three distinct candidates, one recommended scenario, and one minimum validation action with a measurable pass condition.codex exec --ephemeral --sandbox read-onlyinvocation of the Stable Skill produced exactly three candidate rows, one recommended scenario, and quantitative pass conditions.mainCommit3b49b23d441b6ca7e326a86d67a71170cf005237has a wrapper manifest recordingv0.14.0, canonical RepoMetaInFLow/diagnose-enterprise-ai-scenarios, andprompt_runtime_check.v0.1.0tag has no.evozeus-wrapper/wrapper.json(404), so a Stable-Harness end-to-end smoke was not claimed.What was not tested:
Verdict / Review Gate
Risk Checklist
product_tieris an additive Feature Registry field; consumers that ignore unknown fields remain compatible.README.md; both are currentlyDIRTYagainstmain. Their business scope differs, but either PR would need a fresh rebase before reuse.Privacy Checklist
Operational Checklist
Rollback plan
Revert Commits
527474f,37003a5,7ec3db7,f08a61b,b213b8d,3f58f2c, andff0756bfor the source-path boundary and its CI regression, then6e2de4fto restore the previous metadata, Feature Registry order, onboarding copy, and Demo documentation. No user data migration or remote rollback is required.Versioning
https://github.com/MetaInFLow/diagnose-enterprise-ai-scenarios/blob/v0.1.0/SKILL.mdhttps://github.com/MetaInFLow/diagnose-enterprise-ai-scenarios/blob/3b49b23d441b6ca7e326a86d67a71170cf005237/.evozeus-wrapper/wrapper.json4174f9077b6f5bb678e08e57e3cf32b0a1f1122d; verified Harness main3b49b23d441b6ca7e326a86d67a71170cf005237.AI-Assisted Work
Codex inspected the repository and issue evidence, implemented the focused changes, added regression tests, ran all checks listed above, and performed the isolated Stable Skill smoke. Maintainer review owns the final wording, UI UAT, release decision, and follow-through on the Demo Release gate.
Current Review State
Next action: exact-head automatic review and hosted Product CI on
527474f, maintainer review, and Codex desktop Plugin-page UAT. This PR is ready for review and must not be auto-merged.Open reviewer questions: confirm that #45 stays open until the Demo Repo publishes a Harness-containing Stable Release and passes the full managed Demo smoke.