mirror of
https://github.com/affaan-m/ECC.git
synced 2026-09-08 07:37:48 +02:00
feat(install): add guided multi-harness installer (#2649)
* feat(install): add guided Claude plugin setup * fix: support Claude command shims on Windows * feat: support safe Claude plugin scope migration * fix(install): preserve interactive setup terminal * fix(install): auto-migrate setup scope changes * feat(install): add guided multi-harness installer * fix(install): sync Yarn binary metadata * fix(install): handle wizard EOF on Node 18 * ci: allow installer matrix tests to finish * test(install): allow slower PowerShell delegation * fix(install): harden guided provider reconciliation * test(install): harden packaged and local compatibility * chore: prepare guided installer release 2.2.0 * fix(install): report refreshed Codex marketplace state * fix(install): verify managed content provenance * test(install): allow empty Yarn smoke fixture * test(install): invoke Windows package shims safely * fix(install): close cross-platform release gaps * fix(install): require trusted GitHub origins * fix(install): preserve hook profile precedence * refactor(install): centralize trusted GitHub origins * ci: retrigger workflow run after merge of main Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Fable 5
parent
623f2c020f
commit
28e53a0bc1
@@ -1,6 +1,6 @@
|
||||
{
|
||||
"name": "ecc",
|
||||
"version": "2.1.0",
|
||||
"version": "2.2.0",
|
||||
"description": "Harness-native ECC workflows for Codex: shared skills, production-ready MCP configs, and selective-install-aligned conventions for TDD, security scanning, code review, and autonomous development.",
|
||||
"author": {
|
||||
"name": "Affaan Mustafa",
|
||||
|
||||
+13
-14
@@ -1,10 +1,11 @@
|
||||
# plugins/ecc — Codex Repo-Marketplace Plugin Target
|
||||
# plugins/ecc — Legacy Codex Thin-Plugin Artifact
|
||||
|
||||
This directory is the plugin folder that `.agents/plugins/marketplace.json`
|
||||
points at. Codex does not discover plugins whose local marketplace
|
||||
`source.path` is the marketplace root itself (`./`), so the marketplace entry
|
||||
must target a concrete plugin subdirectory — verified against Codex CLI
|
||||
0.137.0 and the official plugin docs (`$REPO_ROOT/plugins/<name>`).
|
||||
This directory is retained as a legacy compatibility artifact. The current
|
||||
`.agents/plugins/marketplace.json` points at the self-contained repository root,
|
||||
which Codex 0.146.0 accepts and copies with all referenced runtime content.
|
||||
Do not point the active marketplace back at this thin directory: its
|
||||
parent-relative references are valid in a checkout but escape the isolated
|
||||
plugin cache after installation.
|
||||
|
||||
## Single source of truth
|
||||
|
||||
@@ -26,12 +27,10 @@ bumps both.
|
||||
|
||||
## Current Codex plugin-mode status
|
||||
|
||||
With this layout, `codex plugin marketplace add affaan-m/ECC` discovers and
|
||||
installs `ecc@ecc`. Runtime skill loading from repo marketplaces is still
|
||||
unreliable upstream — Codex copies only the plugin folder into its install
|
||||
cache, and local/personal marketplace plugins are not always exposed at
|
||||
runtime (see [openai/codex#26037](https://github.com/openai/codex/issues/26037)
|
||||
and [affaan-m/ECC#2128](https://github.com/affaan-m/ECC/issues/2128)).
|
||||
The native marketplace now installs from the repository root. A fresh Codex
|
||||
0.146.0 cache contains the configure skill, shared skills, MCP configuration,
|
||||
hooks, scripts, and assets, and an authenticated session loads the
|
||||
`configure-ecc` skill without hook failures.
|
||||
|
||||
After install, `codex plugin list` is not enough to prove the runtime can load
|
||||
the referenced skills and assets. From an ECC checkout, run:
|
||||
@@ -44,8 +43,8 @@ The check inspects the installed cache under `CODEX_HOME` (or `~/.codex`) and
|
||||
fails if `.codex-plugin/plugin.json` points at files that were not copied into
|
||||
that cache entry.
|
||||
|
||||
Until the upstream discovery issues settle, the supported Codex path is the
|
||||
manual sync flow documented in the README:
|
||||
The manual sync flow remains available only as a separate legacy compatibility
|
||||
path when copied/merged home configuration is explicitly desired:
|
||||
|
||||
```bash
|
||||
npm install && bash scripts/sync-ecc-to-codex.sh
|
||||
|
||||
Reference in New Issue
Block a user