lmer 0.1.0__tar.gz

lmer-0.1.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 20C, LLC
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

lmer-0.1.0/MANIFEST.in

@@ -0,0 +1,7 @@
+include README.md
+include pyproject.toml
+recursive-include src *.py
+recursive-include taskdef *.txt
+prune .venv
+prune container-home
+prune work

lmer-0.1.0/PKG-INFO

@@ -0,0 +1,247 @@
+Metadata-Version: 2.4
+Name: lmer
+Version: 0.1.0
+Summary: Containerized harness for running Claude Code against external repositories
+Author-email: "20C, LLC" <info@20c.com>
+License-Expression: Apache-2.0
+Project-URL: Homepage, https://github.com/lmer2/lmer
+Project-URL: Repository, https://github.com/lmer2/lmer
+Project-URL: Documentation, https://github.com/lmer2/lmer/tree/main/docs
+Project-URL: Issues, https://github.com/lmer2/lmer/issues
+Classifier: Development Status :: 3 - Alpha
+Classifier: Intended Audience :: Developers
+Classifier: Environment :: Console
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Topic :: Software Development
+Classifier: Topic :: Software Development :: Quality Assurance
+Requires-Python: >=3.12
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: python-dotenv>=1.0.0
+Requires-Dist: pre-commit>=3.5.0
+Requires-Dist: requests>=2.25.0
+Requires-Dist: pyyaml>=6.0
+Requires-Dist: jinja2>=3.1.6
+Requires-Dist: fastapi>=0.110.0
+Requires-Dist: uvicorn>=0.27.0
+Provides-Extra: dev
+Requires-Dist: pytest>=7.4.0; extra == "dev"
+Requires-Dist: pytest-cov>=4.1.0; extra == "dev"
+Requires-Dist: flake8>=3.8.0; extra == "dev"
+Requires-Dist: black>=21.0.0; extra == "dev"
+Requires-Dist: mypy>=0.800; extra == "dev"
+Dynamic: license-file
+
+# lmer
+
+**lmer** is a containerized harness for running [Claude Code](https://docs.anthropic.com/en/docs/claude-code) against external repositories.
+
+It clones a target repo into a sandbox container, mounts a known set of development rules and slash commands, and hands the session to Claude with a task-shaped prompt. Tests, pre-commit, and git operations all run inside the container, so the host stays clean and credentials never leak into the target repo's working tree.
+
+Only `chat` ships as a built-in task in [taskdef/](taskdef/). Additional tasks can be loaded from the work-repo or from directories listed in `LMER_TASKDEF_PATHS` — see [docs/TASKDEFS.md](docs/TASKDEFS.md).
+
+> **Note on GitLab vs GitHub support:** Up to this point the priority has been making lmer behave nicely against GitLab — the `gitlab-review` toolset does a lot of heavy lifting to smooth that integration. GitHub generally works, but with this GitHub release the next focus is bringing GitHub interaction up to the same level of polish. Expect rough edges on the GitHub side until that work lands.
+
+## What you get
+
+- A reproducible container image (Oracle Linux 9 Slim, FIPS-capable) with `claude`, `git`, `uv`, and a pinned Python toolchain pre-installed.
+- A consistent ruleset (`AGENTS.md` + `rules/`) injected into Claude's system prompt so behavior is the same across projects: tests before commits, no force-push, show command output, pytest-only, etc.
+- Gate commands (`gate-check`, `gate-commit`, `gate-push`) that enforce those rules at commit-time.
+- Task-specific workflows that load instructions, set up the work environment, and (optionally) drive a follow-up review cycle on the resulting MR.
+
+## Quick Start
+
+The `lmer` CLI provides a safe, containerized environment for AI-assisted development. The typical setup uses an existing Claude.ai subscription (no API key required) and installs from the `prep-release` branch for the latest features.
+
+### 1. Authenticate Claude on the host (subscription users)
+
+If you already use Claude Code with a Claude.ai subscription, run `/login` once on your host machine:
+
+```bash
+claude   # then run /login inside the Claude Code session
+```
+
+This creates `~/.claude/.credentials.json`, which `lmer` automatically mounts into the container — no API key needed.
+
+If you instead authenticate via API key, place it in `~/.lmer/.env` (see [API key alternative](#api-key-alternative) below).
+
+### 2. Install lmer
+
+Pick the branch that matches your needs:
+
+```bash
+# Latest features — may be unstable
+uv tool install lmer --from git+https://github.com/lmer2/lmer@prep-release
+
+# Stable release
+uv tool install lmer --from git+https://github.com/lmer2/lmer@main
+
+# Local / editable (developer mode)
+uv tool install -e lmer --from .
+```
+
+To upgrade later: `uv tool upgrade lmer`.
+
+The container image is pulled automatically on first run from `ghcr.io/lmer2/lmer` — no manual build step is needed. If you can't reach GHCR, or want to develop on the container itself, build it locally from a clone:
+
+```bash
+git clone https://github.com/lmer2/lmer /tmp/lmer-src
+lmer build --local /tmp/lmer-src
+```
+
+Override the pull source with `LMER_REGISTRY=<host>/<path>` for self-hosted registries.
+
+### 3. Configure a work repo
+
+`lmer` requires a **work repo** — a git repository it uses to persist worklogs, gate-check results, and per-project notes across sessions. The `work` CLI inside the container actively `pull`s and `push`es to it, so a remote git repository is required (a bind-mounted local directory would have nothing to push to).
+
+Set up:
+
+1. Create an empty repository on a git host you can read/write — GitLab (cloud or self-hosted) or GitHub both work. A personal/private repo is fine.
+2. Point `lmer` at it and supply a token the container will use for clone/pull/push, via `~/.lmer/.env`:
+
+   ```bash
+   mkdir -p ~/.lmer
+   cat >> ~/.lmer/.env <<'EOF'
+   LMER_WORK_REPO=git@github.com:<you>/lmer-work.git
+
+   # Dedicated work-repo token. Provider-agnostic — works for GitLab,
+   # GitHub, or self-hosted. Highest-priority lookup for the work repo,
+   # so it stays isolated from any per-host tokens used to clone the
+   # target repos you point `lmer chat` at.
+   LMER_WORK_REPO_TOKEN=<your-pat>
+   EOF
+   ```
+
+   The token needs read + write on the work repo. lmer will rewrite the SSH URL to HTTPS-with-token automatically when a token is present.
+
+   SSH instead of HTTPS works too — keep the `git@…` URL, drop the token line, and forward an SSH agent into the container (lmer prints the exact commands when no key is configured).
+
+Subsequent `lmer chat <repo>` runs will clone the work repo into the container at `/work` and push updates back at the end of the session.
+
+### Common options
+
+Targets can be a repo URL, a PR/MR/issue URL (lmer extracts the base repo), a local git path, or omitted to infer from the current directory's git remote:
+
+```bash
+# Remote repo
+lmer chat https://gitlab.com/group/project.git
+
+# GitHub PR or GitLab MR/issue URL — base repo is auto-extracted
+lmer chat https://github.com/org/repo/pull/123
+lmer chat https://gitlab.com/group/project/-/merge_requests/456
+lmer chat https://gitlab.com/group/project/-/issues/31
+
+# Local checkout (extracts remote URL)
+lmer chat /path/to/repo
+
+# Infer from current directory
+cd /path/to/repo && lmer chat
+```
+
+Other useful flags:
+
+```bash
+# Checkout specific branch or ref
+lmer chat https://gitlab.com/group/project.git --branch feature/x
+
+# Get shell access
+lmer chat https://gitlab.com/group/project.git --exec -- bash
+
+# Match host UID for SSH agent permissions
+lmer chat https://gitlab.com/group/project.git --match-uid --exec -- bash
+```
+
+See [docs/LMER-CLI.md](docs/LMER-CLI.md) for complete CLI documentation.
+
+### API key alternative
+
+If you don't have a Claude subscription, place your API key in `~/.lmer/.env`:
+
+```bash
+mkdir -p ~/.lmer
+cat > ~/.lmer/.env <<'EOF'
+CLAUDE_API_KEY=your-claude-key
+GITLAB_TOKEN=your-gitlab-token
+EOF
+```
+
+See [docs/AUTHENTICATION.md](docs/AUTHENTICATION.md) for the full authentication reference.
+
+See [docs/CONTAINER.md](docs/CONTAINER.md) for detailed container documentation.
+
+### Why Oracle Linux 9 / FIPS?
+
+The container is built on `oraclelinux:9-slim-fips`. This base satisfies a FIPS 140-2 compliance requirement: cryptographic operations (TLS, hashing for signed commits, etc.) inside the container must run against a validated module. Oracle Linux 9 ships a validated OpenSSL and exposes `/proc/sys/crypto/fips_enabled`, which `make fips-check` verifies.
+
+If you do not need FIPS, the image still works fine — it just trades a smaller base layer for a validated one. Slimmer Debian/Alpine-based images are not currently supported out of the box; the Containerfile is the single source of truth and contributions for an opt-in alternative base are welcome.
+
+## Developer setup
+
+For working on lmer itself (rather than just using it), clone the repo and build from source:
+
+```bash
+git clone https://github.com/lmer2/lmer ~/Agents/global
+cd ~/Agents/global
+
+# Container workflow (FIPS-compliant)
+make build   # Build the container image
+make lmer    # Run lmer with Claude in a fresh container
+make test    # Run tests locally
+make help    # See all targets
+
+# Or local Python environment
+uv sync
+uv run pre-commit install
+```
+
+> **Path note:** `~/Agents/global` is the conventional host checkout location. Hooks and scripts inside the container refer to `/Agents/global` — that's the **in-container** mount path, populated by lmer at start. You do not need to create `/Agents/global` on the host.
+
+### Rules outside lmer
+
+Rules are injected automatically when running via `lmer` (which uses [libexec/claude-runner.sh](libexec/claude-runner.sh) internally). For standalone `claude` sessions, pass the rules file explicitly:
+
+```bash
+claude --append-system-prompt-file ~/Agents/global/AGENTS.md
+```
+
+User-specific additions: create `~/.lmer/AGENTS.md` — the runner appends it after the workspace config automatically.
+
+## Releasing
+
+Releases to [PyPI](https://pypi.org/project/lmer/) are driven by git tags on `lmer2/lmer`. The full pipeline lives in `.github/workflows/release.yml`.
+
+To cut a release:
+
+1. Bump `version` in `pyproject.toml` (e.g. `0.1.0` → `0.1.1`).
+2. Update `CHANGELOG.yaml` with the release notes.
+3. Commit and merge to `main` through the normal PR flow.
+4. Tag the merge commit and push the tag:
+
+   ```bash
+   git switch main && git pull --ff-only
+   git tag v0.1.1
+   git push origin v0.1.1
+   ```
+
+5. Watch the `Release to PyPI` workflow in the Actions tab. It will:
+   - Verify the tag version matches `pyproject.toml`.
+   - Re-run `pre-commit` and `pytest`.
+   - Build the wheel and sdist with `uv build`.
+   - Publish to PyPI using Trusted Publishing (no stored secrets).
+   - Create a GitHub Release with the artifacts attached.
+
+### Prerequisites (one-time)
+
+- A PyPI **Trusted Publisher** binding must exist for project `lmer` pointing at workflow `release.yml` on `lmer2/lmer`, environment `pypi`. Configure at https://pypi.org/manage/project/lmer/settings/publishing/.
+- A GitHub **environment** named `pypi` must exist on `lmer2/lmer` (Settings → Environments).
+
+Both are set up by the maintainer; they don't need to be touched per release.
+
+## Documentation
+
+See [docs/INDEX.md](docs/INDEX.md) for the full documentation index. Common starting points: [LMER-CLI.md](docs/LMER-CLI.md), [CONTAINER.md](docs/CONTAINER.md), [AUTHENTICATION.md](docs/AUTHENTICATION.md), [TASKDEFS.md](docs/TASKDEFS.md).
+
+The rules Claude follows live in [AGENTS.md](AGENTS.md) and [rules/](rules/) (split by topic: git, testing, code-quality, security, documentation, ci-cd, dependencies). Rule-reading and commit-gate commands (`rgr`, `rgr-git`, `rgrpc`, `pc`, …) are documented in [hooks/README.md](hooks/README.md).

lmer-0.1.0/README.md

@@ -0,0 +1,211 @@
+# lmer
+
+**lmer** is a containerized harness for running [Claude Code](https://docs.anthropic.com/en/docs/claude-code) against external repositories.
+
+It clones a target repo into a sandbox container, mounts a known set of development rules and slash commands, and hands the session to Claude with a task-shaped prompt. Tests, pre-commit, and git operations all run inside the container, so the host stays clean and credentials never leak into the target repo's working tree.
+
+Only `chat` ships as a built-in task in [taskdef/](taskdef/). Additional tasks can be loaded from the work-repo or from directories listed in `LMER_TASKDEF_PATHS` — see [docs/TASKDEFS.md](docs/TASKDEFS.md).
+
+> **Note on GitLab vs GitHub support:** Up to this point the priority has been making lmer behave nicely against GitLab — the `gitlab-review` toolset does a lot of heavy lifting to smooth that integration. GitHub generally works, but with this GitHub release the next focus is bringing GitHub interaction up to the same level of polish. Expect rough edges on the GitHub side until that work lands.
+
+## What you get
+
+- A reproducible container image (Oracle Linux 9 Slim, FIPS-capable) with `claude`, `git`, `uv`, and a pinned Python toolchain pre-installed.
+- A consistent ruleset (`AGENTS.md` + `rules/`) injected into Claude's system prompt so behavior is the same across projects: tests before commits, no force-push, show command output, pytest-only, etc.
+- Gate commands (`gate-check`, `gate-commit`, `gate-push`) that enforce those rules at commit-time.
+- Task-specific workflows that load instructions, set up the work environment, and (optionally) drive a follow-up review cycle on the resulting MR.
+
+## Quick Start
+
+The `lmer` CLI provides a safe, containerized environment for AI-assisted development. The typical setup uses an existing Claude.ai subscription (no API key required) and installs from the `prep-release` branch for the latest features.
+
+### 1. Authenticate Claude on the host (subscription users)
+
+If you already use Claude Code with a Claude.ai subscription, run `/login` once on your host machine:
+
+```bash
+claude   # then run /login inside the Claude Code session
+```
+
+This creates `~/.claude/.credentials.json`, which `lmer` automatically mounts into the container — no API key needed.
+
+If you instead authenticate via API key, place it in `~/.lmer/.env` (see [API key alternative](#api-key-alternative) below).
+
+### 2. Install lmer
+
+Pick the branch that matches your needs:
+
+```bash
+# Latest features — may be unstable
+uv tool install lmer --from git+https://github.com/lmer2/lmer@prep-release
+
+# Stable release
+uv tool install lmer --from git+https://github.com/lmer2/lmer@main
+
+# Local / editable (developer mode)
+uv tool install -e lmer --from .
+```
+
+To upgrade later: `uv tool upgrade lmer`.
+
+The container image is pulled automatically on first run from `ghcr.io/lmer2/lmer` — no manual build step is needed. If you can't reach GHCR, or want to develop on the container itself, build it locally from a clone:
+
+```bash
+git clone https://github.com/lmer2/lmer /tmp/lmer-src
+lmer build --local /tmp/lmer-src
+```
+
+Override the pull source with `LMER_REGISTRY=<host>/<path>` for self-hosted registries.
+
+### 3. Configure a work repo
+
+`lmer` requires a **work repo** — a git repository it uses to persist worklogs, gate-check results, and per-project notes across sessions. The `work` CLI inside the container actively `pull`s and `push`es to it, so a remote git repository is required (a bind-mounted local directory would have nothing to push to).
+
+Set up:
+
+1. Create an empty repository on a git host you can read/write — GitLab (cloud or self-hosted) or GitHub both work. A personal/private repo is fine.
+2. Point `lmer` at it and supply a token the container will use for clone/pull/push, via `~/.lmer/.env`:
+
+   ```bash
+   mkdir -p ~/.lmer
+   cat >> ~/.lmer/.env <<'EOF'
+   LMER_WORK_REPO=git@github.com:<you>/lmer-work.git
+
+   # Dedicated work-repo token. Provider-agnostic — works for GitLab,
+   # GitHub, or self-hosted. Highest-priority lookup for the work repo,
+   # so it stays isolated from any per-host tokens used to clone the
+   # target repos you point `lmer chat` at.
+   LMER_WORK_REPO_TOKEN=<your-pat>
+   EOF
+   ```
+
+   The token needs read + write on the work repo. lmer will rewrite the SSH URL to HTTPS-with-token automatically when a token is present.
+
+   SSH instead of HTTPS works too — keep the `git@…` URL, drop the token line, and forward an SSH agent into the container (lmer prints the exact commands when no key is configured).
+
+Subsequent `lmer chat <repo>` runs will clone the work repo into the container at `/work` and push updates back at the end of the session.
+
+### Common options
+
+Targets can be a repo URL, a PR/MR/issue URL (lmer extracts the base repo), a local git path, or omitted to infer from the current directory's git remote:
+
+```bash
+# Remote repo
+lmer chat https://gitlab.com/group/project.git
+
+# GitHub PR or GitLab MR/issue URL — base repo is auto-extracted
+lmer chat https://github.com/org/repo/pull/123
+lmer chat https://gitlab.com/group/project/-/merge_requests/456
+lmer chat https://gitlab.com/group/project/-/issues/31
+
+# Local checkout (extracts remote URL)
+lmer chat /path/to/repo
+
+# Infer from current directory
+cd /path/to/repo && lmer chat
+```
+
+Other useful flags:
+
+```bash
+# Checkout specific branch or ref
+lmer chat https://gitlab.com/group/project.git --branch feature/x
+
+# Get shell access
+lmer chat https://gitlab.com/group/project.git --exec -- bash
+
+# Match host UID for SSH agent permissions
+lmer chat https://gitlab.com/group/project.git --match-uid --exec -- bash
+```
+
+See [docs/LMER-CLI.md](docs/LMER-CLI.md) for complete CLI documentation.
+
+### API key alternative
+
+If you don't have a Claude subscription, place your API key in `~/.lmer/.env`:
+
+```bash
+mkdir -p ~/.lmer
+cat > ~/.lmer/.env <<'EOF'
+CLAUDE_API_KEY=your-claude-key
+GITLAB_TOKEN=your-gitlab-token
+EOF
+```
+
+See [docs/AUTHENTICATION.md](docs/AUTHENTICATION.md) for the full authentication reference.
+
+See [docs/CONTAINER.md](docs/CONTAINER.md) for detailed container documentation.
+
+### Why Oracle Linux 9 / FIPS?
+
+The container is built on `oraclelinux:9-slim-fips`. This base satisfies a FIPS 140-2 compliance requirement: cryptographic operations (TLS, hashing for signed commits, etc.) inside the container must run against a validated module. Oracle Linux 9 ships a validated OpenSSL and exposes `/proc/sys/crypto/fips_enabled`, which `make fips-check` verifies.
+
+If you do not need FIPS, the image still works fine — it just trades a smaller base layer for a validated one. Slimmer Debian/Alpine-based images are not currently supported out of the box; the Containerfile is the single source of truth and contributions for an opt-in alternative base are welcome.
+
+## Developer setup
+
+For working on lmer itself (rather than just using it), clone the repo and build from source:
+
+```bash
+git clone https://github.com/lmer2/lmer ~/Agents/global
+cd ~/Agents/global
+
+# Container workflow (FIPS-compliant)
+make build   # Build the container image
+make lmer    # Run lmer with Claude in a fresh container
+make test    # Run tests locally
+make help    # See all targets
+
+# Or local Python environment
+uv sync
+uv run pre-commit install
+```
+
+> **Path note:** `~/Agents/global` is the conventional host checkout location. Hooks and scripts inside the container refer to `/Agents/global` — that's the **in-container** mount path, populated by lmer at start. You do not need to create `/Agents/global` on the host.
+
+### Rules outside lmer
+
+Rules are injected automatically when running via `lmer` (which uses [libexec/claude-runner.sh](libexec/claude-runner.sh) internally). For standalone `claude` sessions, pass the rules file explicitly:
+
+```bash
+claude --append-system-prompt-file ~/Agents/global/AGENTS.md
+```
+
+User-specific additions: create `~/.lmer/AGENTS.md` — the runner appends it after the workspace config automatically.
+
+## Releasing
+
+Releases to [PyPI](https://pypi.org/project/lmer/) are driven by git tags on `lmer2/lmer`. The full pipeline lives in `.github/workflows/release.yml`.
+
+To cut a release:
+
+1. Bump `version` in `pyproject.toml` (e.g. `0.1.0` → `0.1.1`).
+2. Update `CHANGELOG.yaml` with the release notes.
+3. Commit and merge to `main` through the normal PR flow.
+4. Tag the merge commit and push the tag:
+
+   ```bash
+   git switch main && git pull --ff-only
+   git tag v0.1.1
+   git push origin v0.1.1
+   ```
+
+5. Watch the `Release to PyPI` workflow in the Actions tab. It will:
+   - Verify the tag version matches `pyproject.toml`.
+   - Re-run `pre-commit` and `pytest`.
+   - Build the wheel and sdist with `uv build`.
+   - Publish to PyPI using Trusted Publishing (no stored secrets).
+   - Create a GitHub Release with the artifacts attached.
+
+### Prerequisites (one-time)
+
+- A PyPI **Trusted Publisher** binding must exist for project `lmer` pointing at workflow `release.yml` on `lmer2/lmer`, environment `pypi`. Configure at https://pypi.org/manage/project/lmer/settings/publishing/.
+- A GitHub **environment** named `pypi` must exist on `lmer2/lmer` (Settings → Environments).
+
+Both are set up by the maintainer; they don't need to be touched per release.
+
+## Documentation
+
+See [docs/INDEX.md](docs/INDEX.md) for the full documentation index. Common starting points: [LMER-CLI.md](docs/LMER-CLI.md), [CONTAINER.md](docs/CONTAINER.md), [AUTHENTICATION.md](docs/AUTHENTICATION.md), [TASKDEFS.md](docs/TASKDEFS.md).
+
+The rules Claude follows live in [AGENTS.md](AGENTS.md) and [rules/](rules/) (split by topic: git, testing, code-quality, security, documentation, ci-cd, dependencies). Rule-reading and commit-gate commands (`rgr`, `rgr-git`, `rgrpc`, `pc`, …) are documented in [hooks/README.md](hooks/README.md).