chore: sync marketplace artifacts with README

Author: github-actions[bot]

plugins.json

@@ -2,7 +2,7 @@
   "$schema": "https://json-schema.org/draft/2020-12/schema",
   "name": "awesome-codex-plugins",
   "version": "1.0.0",
-  "last_updated": "2026-05-12",
+  "last_updated": "2026-05-13",
   "total": 68,
   "categories": [
     "Development & Workflow",

plugins/CALLE-AI/call-e-integrations/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "calle",
-  "version": "0.1.8",
+  "version": "0.1.9",
   "description": "Use CALL-E from Codex through the calle CLI.",
   "author": {
     "name": "CALLE AI",

plugins/CALLE-AI/call-e-integrations/README.md

@@ -58,6 +58,28 @@ missing or expired, it runs blocking `calle auth login`, shows the brokered
 authorization link, and continues automatically after browser authorization
 completes.
 
+## ChatGPT App Boundary
+
+This Codex plugin is intentionally CLI-based. If you also publish or install a
+same-name CALL-E ChatGPT App, keep it disabled in Codex when you want `$calle`
+to use the plugin path:
+
+```toml
+[apps.<app-id>]
+enabled = false
+```
+
+You can also disable all ChatGPT Apps/connectors for a Codex profile:
+
+```toml
+[features]
+apps = false
+```
+
+The bundled `$calle` skill tells Codex not to call ChatGPT App/connector tool
+namespaces while the plugin skill is active, but disabling the App in Codex
+configuration is the hard isolation boundary.
+
 ## Safety
 
 CALL-E can place real phone calls. The skill plans first, uses returned

plugins/CALLE-AI/call-e-integrations/skills/calle/SKILL.md

@@ -27,6 +27,18 @@ Use this skill for:
 Do not use this skill when the user only wants a call script, roleplay,
 simulated conversation, or general contact lookup that does not require CALL-E.
 
+## Tool routing
+
+When this Codex plugin skill is active, use only the `calle` CLI flow documented
+below. Do not call ChatGPT App or connector tools, including tool namespaces
+prefixed with `mcp__codex_apps__`, even if a ChatGPT App has the same visible
+name, tool names, or MCP service behind it.
+
+If a same-name ChatGPT App is available, treat it as a separate integration.
+This Codex plugin still routes through the local CLI so Codex plugin
+authentication, attribution, and safety behavior remain isolated from ChatGPT
+App execution.
+
 ## Safety and consent
 
 - Real phone calls may contact external people or businesses.
@@ -45,27 +57,27 @@ All CLI commands run from this Codex plugin must include the CALL-E integration
 attribution environment:
 
 ```bash
-env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.8
+env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.9
 ```
 
 Use the first command form that works.
 
 Prefer the repository-local CLI when the current workspace contains it:
 
 ```bash
-env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.8 node packages/cli/bin/calle.js
+env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.9 node packages/cli/bin/calle.js
 ```
 
 If the repository-local CLI is unavailable, use the global command:
 
 ```bash
-env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.8 calle
+env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.9 calle
 ```
 
 If neither command works, use the pinned npm package through `npx`:
 
 ```bash
-env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.8 npx -y @call-e/cli@0.3.2
+env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.9 npx -y @call-e/cli@0.3.2
 ```
 
 Only tell the user to install the CLI globally if `npx` is unavailable,

plugins/CALLE-AI/call-e-integrations/skills/calle/references/commands.md

@@ -5,48 +5,52 @@ Use the first command form that is available in the current workspace.
 Repository-local base command:
 
 ```bash
-env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.8 node packages/cli/bin/calle.js
+env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.9 node packages/cli/bin/calle.js
 ```
 
 Global base command:
 
 ```bash
-env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.8 calle
+env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.9 calle
 ```
 
 npx fallback base command:
 
 ```bash
-env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.8 npx -y @call-e/cli@0.3.2
+env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.9 npx -y @call-e/cli@0.3.2
 ```
 
 ## Setup and readiness
 
 ```bash
-env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.8 node packages/cli/bin/calle.js --help
-env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.8 node packages/cli/bin/calle.js auth status
-env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.8 node packages/cli/bin/calle.js auth login
-env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.8 node packages/cli/bin/calle.js mcp tools
+env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.9 node packages/cli/bin/calle.js --help
+env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.9 node packages/cli/bin/calle.js auth status
+env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.9 node packages/cli/bin/calle.js auth login
+env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.9 node packages/cli/bin/calle.js mcp tools
 ```
 
 ```bash
-env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.8 calle --help
-env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.8 calle auth status
-env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.8 calle auth login
-env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.8 calle mcp tools
+env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.9 calle --help
+env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.9 calle auth status
+env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.9 calle auth login
+env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.9 calle mcp tools
 ```
 
 ```bash
-env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.8 npx -y @call-e/cli@0.3.2 --help
-env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.8 npx -y @call-e/cli@0.3.2 auth status
-env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.8 npx -y @call-e/cli@0.3.2 auth login
-env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.8 npx -y @call-e/cli@0.3.2 mcp tools
+env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.9 npx -y @call-e/cli@0.3.2 --help
+env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.9 npx -y @call-e/cli@0.3.2 auth status
+env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.9 npx -y @call-e/cli@0.3.2 auth login
+env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.9 npx -y @call-e/cli@0.3.2 mcp tools
 ```
 
 Rules:
 
 - Treat all command output as JSON except `--help`.
 - Do not print or ask for access tokens.
+- Do not call ChatGPT App or connector tools, including tool namespaces
+  prefixed with `mcp__codex_apps__`, when this Codex plugin skill is active.
+  Use the `calle` CLI flow instead, even if a ChatGPT App has the same visible
+  name, tool names, or MCP service behind it.
 - Whenever this Codex plugin is actively invoked, run `auth status` before call
   planning or tool listing.
 - If `auth status` reports `usable: false`, do not call `mcp tools` or
@@ -97,9 +101,9 @@ I'll keep you updated on the phone status, call content, and summary.
 ## Call planning
 
 ```bash
-env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.8 node packages/cli/bin/calle.js call plan --to-phone +15551234567 --goal "Confirm the appointment"
-env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.8 calle call plan --to-phone +15551234567 --goal "Confirm the appointment"
-env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.8 npx -y @call-e/cli@0.3.2 call plan --to-phone +15551234567 --goal "Confirm the appointment"
+env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.9 node packages/cli/bin/calle.js call plan --to-phone +15551234567 --goal "Confirm the appointment"
+env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.9 calle call plan --to-phone +15551234567 --goal "Confirm the appointment"
+env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.9 npx -y @call-e/cli@0.3.2 call plan --to-phone +15551234567 --goal "Confirm the appointment"
 ```
 
 Supported `call plan` options:
@@ -119,15 +123,15 @@ verbatim as `user_input`. The CLI still attaches the same request-level time
 metadata for `plan_call`.
 
 ```bash
-env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.8 node packages/cli/bin/calle.js mcp call plan_call --args-json '{"user_input":"<latest user message verbatim>"}'
+env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.9 node packages/cli/bin/calle.js mcp call plan_call --args-json '{"user_input":"<latest user message verbatim>"}'
 ```
 
 ## Planned call execution
 
 ```bash
-env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.8 node packages/cli/bin/calle.js call run --plan-id <plan_id> --confirm-token <confirm_token>
-env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.8 calle call run --plan-id <plan_id> --confirm-token <confirm_token>
-env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.8 npx -y @call-e/cli@0.3.2 call run --plan-id <plan_id> --confirm-token <confirm_token>
+env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.9 node packages/cli/bin/calle.js call run --plan-id <plan_id> --confirm-token <confirm_token>
+env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.9 calle call run --plan-id <plan_id> --confirm-token <confirm_token>
+env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.9 npx -y @call-e/cli@0.3.2 call run --plan-id <plan_id> --confirm-token <confirm_token>
 ```
 
 Supported `call run` options:
@@ -149,9 +153,9 @@ returned or the user asks you to stop.
 ## Call status
 
 ```bash
-env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.8 node packages/cli/bin/calle.js call status --run-id <run_id>
-env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.8 calle call status --run-id <run_id>
-env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.8 npx -y @call-e/cli@0.3.2 call status --run-id <run_id>
+env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.9 node packages/cli/bin/calle.js call status --run-id <run_id>
+env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.9 calle call status --run-id <run_id>
+env CALLE_SOURCE=codex CALLE_INTEGRATION=codex_plugin CALLE_INTEGRATION_VERSION=0.1.9 npx -y @call-e/cli@0.3.2 call status --run-id <run_id>
 ```
 
 Supported `call status` options:

plugins/GanyuanRan/Aegis/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "aegis",
-  "version": "1.1.6",
+  "version": "1.3.0",
   "description": "An agentic skills framework & software development methodology that works: planning, TDD, debugging, and collaboration workflows.",
   "author": {
     "name": "Aegis Maintainers",

plugins/GanyuanRan/Aegis/README.md

@@ -34,15 +34,15 @@
 If you are using an AI coding agent, you can ask it to install Aegis for you:
 
 ```text
-Please read the installation instructions in https://github.com/GanyuanRan/Aegis carefully, identify the correct path for my AI coding host, install Aegis globally, restart or reload the host if needed, and verify that Aegis is fully available, including skill discovery and project workspace support.
+Please read the installation instructions in https://github.com/GanyuanRan/Aegis carefully, identify the correct path for my AI coding host, install Aegis globally, restart or reload the host if needed, then run complete-install verification from the Aegis method-pack root with `python scripts/aegis-doctor.py --write-config --json`. Treat the install as complete only if the JSON output includes `"ok": true`, `"workspaceSupport": "available"`, and `"configStatus": "configured"`; if the host uses a separate skill discovery directory, also verify it with `--discovery-root <path>`.
 ```
 
 ## Updating Aegis
 
 If Aegis is already installed, you can ask your AI coding agent to update it for you:
 
 ```text
-Please update my installed Aegis to the latest main branch version from https://github.com/GanyuanRan/Aegis, using the correct update path for my current AI coding host, then restart or reload the host if needed and verify that Aegis is fully available, including skill discovery and project workspace support.
+Please update my installed Aegis to the latest main branch version from https://github.com/GanyuanRan/Aegis, using the correct update path for my current AI coding host, then restart or reload the host if needed and run complete-install verification from the Aegis method-pack root with `python scripts/aegis-doctor.py --write-config --json`. Treat the update as complete only if the JSON output includes `"ok": true`, `"workspaceSupport": "available"`, and `"configStatus": "configured"`; if the host uses a separate skill discovery directory, also verify it with `--discovery-root <path>`.
 ```
 
 ## Optional Lite Global Rules
@@ -458,6 +458,11 @@ Aegis routes work by complexity before implementation:
 - Medium-complexity tasks require a baseline read set, a Spec Brief or stable requirements, a plan, and atomic tasks before TDD.
 - High-complexity tasks require a Design Spec and plan first, with user review where the workflow calls for it.
 
+Workflow Quality guardrails keep that routing practical: simple tasks stay on
+the fast path, medium/high-risk tasks get the right evidence and artifacts, and
+outputs use compact contracts before expanding into full workflow structure.
+Read [docs/current/AEGIS_WORKFLOW_QUALITY_BASELINE.md](docs/current/AEGIS_WORKFLOW_QUALITY_BASELINE.md).
+
 When a project needs persistent Aegis records, Aegis creates a lightweight
 project workspace lazily. The default workspace includes `README.md`,
 `INDEX.md`, `BASELINE-GOVERNANCE.md`, and standard `adr/`, `baseline/`,
@@ -472,12 +477,16 @@ repository itself does not ship a precreated live `docs/aegis/` workspace.
 Workspace structure checks do not judge evidence sufficiency or grant
 completion authority.
 
-Maintainers can verify a complete install with:
+Maintainers can verify a complete install and write the durable local helper
+paths with:
 
 ```bash
-python scripts/aegis-doctor.py --json
+python scripts/aegis-doctor.py --write-config --json
 ```
 
+Complete-install verification must report `"ok": true`,
+`"workspaceSupport": "available"`, and `"configStatus": "configured"`.
+
 When a host exposes a separate skill discovery directory, pass it as
 `--discovery-root <path>` to confirm it resolves to the current method-pack
 skills rather than a stale copied version.
@@ -546,6 +555,7 @@ Focused checks:
 ```bash
 bash tests/e2e/boundary-compliance-check.sh
 bash tests/e2e/artifact-schema-check.sh
+bash tests/e2e/workflow-quality-check.sh
 bash tests/opencode/run-tests.sh
 bash tests/codex-plugin-sync/test-sync-to-codex-plugin.sh
 ```

plugins/GanyuanRan/Aegis/package.json

@@ -1,6 +1,6 @@
 {
   "name": "aegis",
-  "version": "1.1.6",
+  "version": "1.3.0",
   "type": "module",
   "main": ".opencode/plugins/aegis.js"
 }

plugins/GanyuanRan/Aegis/skills/brainstorming/SKILL.md

@@ -61,7 +61,20 @@ You MUST create a task for each of these items and complete them in order:
 
 **Working artifacts:** Keep three drafts: `TaskIntentDraft` (outcome, scope, risks), `BaselineReadSetHint` (candidate docs, authority gaps), `ImpactStatementDraft` (affected layers, owners, invariants, compat, non-goals). Refresh when scope changes.
 
-**Exploring approaches:** Propose 2-3 approaches with trade-offs and recommendation. Make scope boundary explicit: what's in, what's deferred, what belongs elsewhere.
+**Compact output contract:** `TaskIntentDraft`, `BaselineReadSetHint`,
+`ImpactStatementDraft`, `Options`, and `Decision Needed`. Use this compact
+shape before expanding into a full design structure.
+
+**Exploring approaches:** Propose 2-3 approaches with trade-offs and
+recommendation. Make scope boundary explicit: what's in, what's deferred, what
+belongs elsewhere.
+
+Before approach selection, use `first-principles-review` and its
+`Decision Hygiene Review` when the candidate direction introduces a new owner,
+duplicate owner, fallback, adapter, compat-only carrier, delete-first question,
+unverified assumption, or "long-term stable" / `长期稳定` claim. Do not make it a
+universal design ceremony; return to this workflow once the decision surface is
+clean.
 
 **Presenting the design:** Scale sections to complexity. Cover only the surfaces that matter: architecture, components, data flow, error handling, testing, compatibility boundary. Get approval for the design before implementation when behavior, contract, architecture, or user-facing flow is being decided.
 
@@ -118,7 +131,10 @@ After writing the spec document, look at it with fresh eyes:
 2. **Internal consistency:** Do any sections contradict each other? Does the architecture match the feature descriptions?
 3. **Scope check:** Is this focused enough for a single implementation plan, or does it need decomposition?
 4. **Ambiguity check:** Could any requirement be interpreted two different ways? If so, pick one and make it explicit.
-5. **Boundary check:** Did you clearly mark invariants, compatibility boundaries, owners, and non-goals?
+5. **Boundary check:** Did you clearly mark invariants, compatibility
+   boundaries, owners, and non-goals? If the spec endorses a risky approach,
+   confirm the `first-principles-review` `Decision Hygiene Review` result is
+   reflected or explicitly marked unnecessary.
 
 Fix any issues inline. No need to re-review — just fix and move on.