ci: GitHub-only releases, no PyPI publishing

Author: wowi42

.github/workflows/release.yml

@@ -3,8 +3,7 @@ name: release
 # Automated semver releases driven by conventional commits (release-please):
 # every push to main updates a release PR that bumps pyproject.toml and
 # CHANGELOG.md; merging it creates the vX.Y.Z tag + GitHub Release, which
-# triggers the publish job below (PyPI via trusted publishing + dists
-# attached to the GitHub Release).
+# triggers the publish job below (dists attached to the GitHub Release).
 on:
   push:
     branches: [main]
@@ -13,7 +12,6 @@ permissions:
   contents: write
   pull-requests: write
   issues: write
-  id-token: write # trusted publishing to PyPI
 
 jobs:
   release-please:
@@ -76,9 +74,6 @@ jobs:
       - name: Build distributions
         run: uv build
 
-      - name: Publish to PyPI
-        uses: pypa/gh-action-pypi-publish@release/v1
-
       - name: Attach distributions to the GitHub Release
         env:
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}

README.md

@@ -77,8 +77,7 @@ Targets macOS and Linux; Windows is best-effort.
 uv tool install --force git+https://github.com/KalvadTech/lecode
 ```
 
-(If the `lecode` name is ever taken on PyPI, the package is also published
-as `lecode-agent` — the command stays `lecode`.)
+lecode is distributed from this repository only — it is not on PyPI.
 
 ## Quickstart
 
@@ -234,8 +233,8 @@ Releases are automated with [release-please](https://github.com/googleapis/relea
 and follow semver, driven by conventional commits: `fix:` → patch, `feat:` →
 minor, `feat!:` (or any `!`) → major. Every push to `main` updates a release
 PR that bumps `pyproject.toml` and `CHANGELOG.md`; merging that PR creates the
-`vX.Y.Z` tag and the GitHub Release, then publishes the dists to PyPI and
-attaches them to the release.
+`vX.Y.Z` tag and the GitHub Release, with the built dists (wheel + sdist)
+attached to the release. Nothing is published to PyPI.
 
 ## License
 

docs/build-plan.md

@@ -24,8 +24,8 @@ Design stance (from kon): the default harness stays tiny — **default system pr
 ~300 tokens**, project context loaded externally via AGENTS.md files and skills. A rich,
 detailed prompt (personas, mode prompts) is available as a config option.
 
-(Release-time check: if `lecode` is taken on PyPI, publish as `lecode-agent` while
-keeping the `lecode` command name.)
+(Release: GitHub-only — git tag + GitHub Release via release-please; not
+published to PyPI.)
 
 ## Feature lineage
 
@@ -121,7 +121,7 @@ portal.
   `rtk` compacts `bash` output (`rtk rewrite`, fail-open with 5s timeout on individual
   rewrites). Startup verifies all three exist on PATH and exits with install
   instructions otherwise (exit code 2). No auto-download, no fallback code paths.
-- **Packaging**: PyPI package, `uv tool install`.
+- **Packaging**: installable from the GitHub repo via `uv tool install` (not on PyPI).
 - **Tooling**: `uv`, `pytest` + `pytest-asyncio` + `respx`, `ruff`, `pydantic` v2,
   `typer`.
 
@@ -421,9 +421,9 @@ lecode/
     diagnostics-in-results, `lsp_diagnostics`), then MCP client with Exa/context7
     auto-config (largest, own sub-phase).
 11. **Onboarding + release** — `--setup` wizard, first-run defaults, `/init`, `/welcome`,
-    docs (including fd/rg/rtk install instructions); PyPI publish workflow (verify the
-    `lecode` name, else `lecode-agent`); clean-machine `uv tool install` → setup →
-    real coding task; full CI green.
+    docs (including fd/rg/rtk install instructions); automated release workflow
+    (release-please: semver tag + GitHub Release, no PyPI); clean-machine
+    `uv tool install` → setup → real coding task; full CI green.
 
 ## Sizing