fix(release): repair shim publishing and distribute synced package READMEs

[rhuanbarreto]

Summary

The first run of the multi-ecosystem Publish Shims workflow at v0.40.0 (run 26601268709) failed for three ecosystems. This PR fixes each root cause and, while in the area, gives every shim package a README that is kept identical to the canonical root README.md.

CI publish fixes

• PyPI — python -m build failed: OSError: Readme file does not exist: README.md. pyproject.toml declares readme = "README.md" but no file existed. Added shims/pypi/README.md.
• RubyGem — bundle exec rake release ran from the repo root (Could not locate Gemfile) and there was no release task. Now runs in shims/rubygem (working-directory + bundler-cache: true on setup-ruby, working-directory on release-gem) and a Rakefile provides the task via bundler/gem_tasks.
• Maven — the job hit the 15-minute timeout. The bundle uploaded fine, then hung on <waitUntil>published</waitUntil> waiting for Sonatype to finish publishing. Switched to <waitUntil>validated</waitUntil> (with autoPublish=true) so the build returns after validation and publishing completes async.

Package READMEs + sync

• Copied the root README.md into every shim package (go, pypi, nuget, rubygem, maven). npm needs no copy — it publishes the root README directly.
• Wired packaging that consumes a README: NuGet <PackageReadmeFile> + pack item; RubyGem gemspec spec.files.
• Automated sync via the release pipeline: .simple-release.js bump() now propagates root README.md to every shim copy during the release commit, mirroring the existing version-sync blocks.
• CI safety net: new ARCH-013/shim-readme-sync rule fails archgate check if any shim README drifts from root (line-ending/trailing-whitespace normalized) — catches drift between releases. ARCH-013 updated to document README synchronization.

Reviewer notes

• README sync has two layers: the bump hook regenerates copies at release time; the shim-readme-sync rule blocks mid-cycle drift in PRs (with a cp fix hint).
• v0.40.0's maven bundle did upload before the timeout (deploymentId d7671fb1) and was set to auto-publish, so 0.40.0 may already be on Maven Central. The publish jobs are not idempotent across a full re-run (publish-go-tag/publish-nuget/maven will hit "already exists") — recommend letting these fixes apply to the next version bump rather than re-running v0.40.0.

Test plan

• bun run validate passes — lint, typecheck, format, 1212 tests, ADR check (30/30), knip, build
• shim-readme-sync rule verified to fail on drift and pass when synced
• .simple-release.js imports without error after the change
• Confirm next release publishes successfully to PyPI, RubyGems, and Maven Central

[cloudflare-workers-and-pages]

Deploying archgate-cli with    Cloudflare Pages

Latest commit:	7034286
Status:	✅  Deploy successful!
Preview URL:	https://764c6784.archgate-cli.pages.dev
Branch Preview URL:	https://claude-intelligent-leavitt-c.archgate-cli.pages.dev

View logs

[github-actions]

Code Coverage

Metric	Value
Lines	90.0% (6550 / 7278)
Threshold	90% minimum — met
Platforms	Linux + Windows

Full HTML report available in workflow artifacts.

Per-directory breakdown

Directory	Coverage	Lines
src/commands/	88.1%	2069 / 2348
src/engine/	93.1%	1207 / 1297
src/formats/	100.0%	141 / 141
src/helpers/	89.7%	3133 / 3492