fix(workspace): unpin Compound Engineering in engineering example

[christso]

The engineering workspace pins Compound Engineering to a release, so updates keep reinstalling that release. Remove the portable ref and the Pi-native Git source's release suffix so both follow the upstream default branch. Keep the other Pi packages pinned, and update the README and existing sync-plan test to match.

Validation:

• CI passed all jobs, including the full test suite on the repository-pinned Bun version, docs, build/package smoke tests, lint, typecheck, Node 24, and Windows command checks.
• Focused parser, Pi source, and sync-planning tests: 49 passed. The old engineering test failed on the removed pin before its assertions were updated.
• bun run typecheck, bun run lint, bun run build, and git diff --check passed.
• Default bun test on local Bun 1.4.3: 2,198 passed, 7 skipped, one existing cross-file mock leak in native/types failed. Reproduced using only unchanged native-marketplace-registration.test.ts and types.test.ts; types.test.ts passes alone. bun test --isolate fixes that failure but exposes another existing mock-export leak (checkRepositoryHealth) in unchanged workspace-modify-dedup.test.ts: 2,196 passed, 7 skipped, 1 failure/error. The repository-pinned Bun 1.4.0 CI run is the authoritative full-suite check; baseline main CI is green.
• Read-only code review: complete, ready to merge; run 20261015-225236-6b8ddb91. The affected test finding was fixed and verified; no unresolved findings.

Manual E2E setup and evidence

Built the CLI with bun run build. Used fresh HOME and project directories under /tmp/allagents-unpin-e2e-*, with ALLAGENTS_TEST_HOME, XDG paths, CODEX_HOME, and PI_CODING_AGENT_DIR pointed inside the fixture. Global Git configuration was disabled. The full example was copied into the fixture for inventory; installation then selected just the two changed Compound Engineering declarations, retaining the template's universal client, to avoid installing unrelated packages. A saved Pi trust decision applied only to this temporary project. No provider credentials or setup hooks were used.

From the temporary project, ran the real built entrypoint with the isolated environment:

<worktree>/dist/index.js --json plugin list
<worktree>/dist/index.js --json update --scope project  # portable declaration
<worktree>/dist/index.js --json update --scope project  # portable + Pi-native declarations
<worktree>/dist/index.js --json plugin list

Observed 36 portable skill directories, including ce-work and ce-plan. Sync state recorded resolvedRef: HEAD and upstream commit fac349c0c31a543d497fd4825af9b44bdb7e7dfe, with no requested ref. Pi wrote git:github.com/EveryInc/compound-engineering-plugin to its project package settings, and AllAgents recorded the same native identity as managed. A pre-existing user-owned skill remained unchanged. The remaining template plugin declarations matched origin/main exactly.

[cloudflare-workers-and-pages]

Deploying allagents with    Cloudflare Pages

Latest commit:	9469f5a
Status:	✅  Deploy successful!
Preview URL:	https://63b4bd79.allagents.pages.dev
Branch Preview URL:	https://fix-workspace-engineering-la.allagents.pages.dev

View logs