lanegate 1.0.0__tar.gz

lanegate-1.0.0/.gitignore

@@ -0,0 +1,26 @@
+# Python
+__pycache__/
+*.py[cod]
+*.egg-info/
+*.egg
+dist/
+build/
+venv/
+.venv/
+
+# LaneGate local state
+.lanegate/*
+!.lanegate/tickets/
+!.lanegate/tickets/*
+.lanegate/executor-runs/
+!.lanegate/notes/
+.lanegate/notes/*
+!.lanegate/notes/.gitkeep
+worktrees/
+*-context-log.jsonl
+
+# Go TUI compiled binary (go build -o lanegate-tui ./tui/cmd/lanegate-tui, run from repo root)
+/lanegate-tui
+
+# Claude Code local overrides (personal, never shared)
+.claude/settings.local.json

lanegate-1.0.0/.lanegate.yml.example

@@ -0,0 +1,243 @@
+# .lanegate.yml — project configuration for lanegate
+# Copy this file to .lanegate.yml in your repo root and edit to taste.
+# Or run `lanegate init` to generate a config interactively.
+
+ticket_prefix: TICK          # TICK-NNN, FEAT-NNN, BUG-NNN, TASK-NNN, etc.
+tickets_dir: .lanegate/tickets
+worktrees_dir: .lanegate/worktrees
+
+# Legacy shorthand: who writes the code when `steps.implement.driver` is not set.
+executor: claude             # claude | claude-subagent | claude-process | aider | openhands | codex | ollama
+
+# Legacy shorthand: who reviews the code when `steps.review.driver` is not set
+# (optional — defaults to executor if omitted).
+# Set to a different executor for model review, or `human` when you want a
+# person to record each review verdict.
+# For a batch-level human gate without changing the reviewer, run:
+#   lanegate orchestrate --human-review final
+# For per-ticket human verdicts, uncomment `reviewer: human` and run:
+#   lanegate orchestrate --human-review per_ticket
+# reviewer: human
+
+# --- Multi-agent dispatch (optional) ---
+#
+# Define named driver instances. Each driver is an invocation of an agent type
+# with specific settings. Use driver names in `steps:` or per-ticket
+# `executor:` / `reviewer:` frontmatter.
+drivers:
+  # Claude via subprocess — good for high-quality review.
+  claude-main:
+    type: claude-process
+    model: claude-sonnet-4-6
+
+  # Ollama REST driver — text-only, no file-editing/commit capability of its
+  # own (Ollama is a model server, not a coding agent). Only useful for
+  # text-only steps like analyze. For local *coding*, use aider-local below.
+  ollama-qwen:
+    type: ollama
+    model: qwen2.5-coder:32b
+    base_url: http://localhost:11434   # default; omit if using the standard port
+
+  # Aider with a local model — no hosted rate limits; useful for bulk
+  # implementation. This is the validated local/offline coding path, since
+  # Aider applies and commits edits itself. ollama_chat/ (not ollama/) is the
+  # recommended prefix for instruct-tuned coding models.
+  aider-local:
+    type: aider
+    model: ollama_chat/qwen2.5-coder:14b
+    provider: ollama
+    context_window_tokens: 32768   # local models have a finite context window
+    flags: ["--no-pretty", "--no-stream", "--yes-always", "--no-check-update",
+            "--no-analytics", "--no-show-model-warnings"]
+
+  # Aider on a rented/remote GPU box, reached through an SSH tunnel rather
+  # than exposing Ollama's (unauthenticated) API port publicly:
+  #   ssh -N -L 11435:localhost:11434 <user>@<remote-host>
+  #   export OLLAMA_API_BASE=http://localhost:11435   # aider reads this directly
+  # Route to it with a ticket-level `executor: aider-remote` override rather
+  # than the global `executor:` default or a pool — a single local model
+  # instance isn't necessarily the right tier for every ticket.
+  aider-remote:
+    type: aider
+    model: ollama_chat/qwen3-coder:30b-a3b-q4_K_M
+    provider: ollama
+    context_window_tokens: 32768
+
+  # OpenAI Codex CLI.
+  codex-cloud:
+    type: codex
+    model: o4-mini
+
+# Route each pipeline step to a specific driver.
+# Omit this block to use the top-level legacy `executor:` / `reviewer:` fields.
+steps:
+  analyze:
+    driver: claude-main     # strong model for ticket analysis
+  implement:
+    driver: aider-local     # local model handles bulk coding
+  review:
+    driver: claude-main     # Claude reviews for quality
+
+# Legacy shorthand: max tickets the orchestrator runs in parallel.
+# Effective batch = min(touch-disjoint candidates, max_parallel)
+max_parallel: 2
+
+# What to do when the executor hits a rate limit / quota error mid-run.
+# halt   (default) — hibernate the ticket, print instructions, stop the run.
+#                     You re-run `lanegate orchestrate` manually once the limit clears.
+# resume            — same hibernate, but also spawns a detached `lanegate resume-watch`
+#                     daemon that polls with capped exponential backoff and re-runs
+#                     `lanegate orchestrate` automatically once the limit clears.
+on_rate_limit: halt
+
+# Backoff settings for the resume-watch daemon (only used when on_rate_limit: resume).
+# ceiling_s: null polls forever; set it (e.g. 21600 for 6h) to give up after that
+# many total seconds and fall back to printing manual-resume instructions instead.
+rate_limit_resume:
+  initial_backoff_s: 300   # first retry after 5 minutes
+  max_backoff_s: 7200      # backoff never grows past 2 hours between retries
+  ceiling_s: null
+
+# Chain a ticket's pipeline steps onto one CLI session via --resume (Claude
+# subprocess executors only) instead of every step starting cold. The
+# per-invocation fixed bootstrap cost (system prompt/tools) only needs to be
+# cache-written once per session, not once per process — a measured ~9x cost
+# reduction on a resumed call vs a cold one (see
+# docs/session-usage-investigation.md). implement resumes analyze's session;
+# fix resumes implement's (or a prior fix pass's, on a second autofix cycle);
+# drift_check resumes fix's. Gated per-resume by max_session_age_s/
+# max_session_tokens using real step_costs data, since a resume past the
+# server's prompt-cache TTL re-pays cache-write price for the whole
+# accumulated session instead of just the fixed bootstrap — potentially
+# costing *more* than a cold dispatch would have.
+session_chaining:
+  enabled: true             # master switch
+  # Review stays independent (cold, no --resume) by default — a reviewer
+  # that inherits the implementer's exact reasoning trail undermines the
+  # point of an independent check. Opt in only if you want the cost saving
+  # more than that independence.
+  chain_review: false
+  max_session_age_s: 2700     # don't resume past this (45 min; safety
+                               # margin under the CLI's 1h cache TTL)
+  max_session_tokens: 150000  # don't resume past this either — dispatch
+                               # fresh instead once a session has grown this large
+
+# Phone alert (via ntfy.sh) when `lanegate orchestrate` looks stuck: dead process,
+# stale executor heartbeat, or the loop halted with tickets still waiting in
+# needs_review/blocked/failed/hibernated. Also used by resume-watch to push on
+# rate-limit hit / give-up / resumed. Set ntfy_topic and run `lanegate notify-watch`
+# (see docs/config-reference.md#phone-alerts-for-stuck-runs-notify-watch).
+# ntfy_topic is credential-like (anyone who knows it can read/post to your
+# channel) — if this file is git-tracked, leave it null here and set the
+# LANEGATE_NTFY_TOPIC env var instead; it overrides this value when set.
+notify:
+  ntfy_topic: null         # null = log only, no pushes sent
+  poll_seconds: 60
+  heartbeat_stale_seconds: 180
+
+# Legacy shorthand: per-executor overrides (replace the global, not additive).
+# `flags` are prepended to the executor command when dispatching a ticket.
+# The flags below enable headless/autonomous operation — remove them if you
+# want the executor to prompt for approval on each action (supervised mode).
+# `claude` shown here uses the scoped default (`lanegate init` writes this
+# automatically): it auto-approves only the tool categories orchestrate needs
+# and leaves everything else (WebFetch, WebSearch, MCP tools, ...) gated. The
+# fully-open alternative, flags: ["--dangerously-skip-permissions"], disables
+# every permission check process-wide — a valid choice for setups like a
+# disposable CI container, but not the default. See
+# docs/security-model.md#headless-permission-options-for-the-claude-executor.
+executors:
+  claude:  { max_parallel: 3, flags: ["--allowedTools", "Bash,Edit,Write,Read,Glob,Grep"] }
+  aider:   { max_parallel: 1, flags: ["--yes-always"] }
+  codex:   { max_parallel: 3, flags: ["--approval-policy=never"] }
+  ollama:  { max_parallel: 1, models: { analyze: llama3.1 } }  # text-only; see drivers: above for local coding
+
+# Optional: distribute tickets across more than one account of the same
+# executor type (see "Named executor instances" + "Executor pools" in
+# docs/config-reference.md). Uncomment and define named instances under
+# executors: (each needs its own `type:` and usually its own `api_key_env:`)
+# before enabling a pool that references them.
+# pools:
+#   default:
+#     executors: [claude-1, claude-2]
+#     strategy: least-loaded   # or round-robin
+# default_pool: default
+
+# Files/patterns where overlapping tickets cannot run in parallel.
+# Leave empty if your project has no shared core files.
+core_files: []
+core_patterns: []
+
+# Visual verification for UI-facing tickets. LaneGate does not run a browser or
+# a dev server itself — this only tells the implement/review prompts (a) which
+# touched files count as "UI" so the visual-verification instructions get
+# added, and (b) how to reach the running app. The agent still needs its own
+# browser/screenshot tooling (e.g. a Playwright MCP server, an in-session
+# browser subagent) configured on the executor side — that's outside LaneGate.
+# `groups` is a list because a monorepo can have several distinct UI areas
+# (separate frontend apps, or e.g. an AEM ui.frontend clientlib vs. the AEM
+# author/publish instance itself) each reachable at a different dev
+# server/URL. Leave groups empty (the default) to disable this entirely.
+verification:
+  groups: []
+  # groups:
+  #   - patterns: ["apps/web/**", "**/*.tsx"]
+  #     dev_server: "npm run dev"
+  #     url: "http://localhost:3000"
+  #   - patterns: ["apps/admin/**"]
+  #     dev_server: "npm run dev:admin"
+  #     url: "http://localhost:4000"
+
+# Repo-local coding practices to include in analyze/implement/review prompts.
+# By default LaneGate also discovers common files like AGENTS.md, CLAUDE.md,
+# .github/copilot-instructions.md, .cursorrules, and CONTRIBUTING.md.
+# Set `project_guidance: false` to disable this prompt context.
+project_guidance:
+  include_defaults: true
+  files: []
+  max_bytes: 20000
+
+# Statuses during which a ticket's `touches` stay locked (held until merge).
+lock_statuses: [in_progress, code_complete, in_review]
+
+# Deterministic checks before lifecycle transitions.
+# A failing command blocks the transition.
+# Supported examples include: pytest, npm test, cargo test, go test, make lint,
+# and executable scripts such as scripts/run-tests.sh.
+safeguards:
+  pre_complete:
+    - pytest
+  pre_merge:
+    - pytest
+  # Runs from the merged control checkout during `lanegate validate`.
+  # When configured, `lanegate done` requires validation first.
+  post_merge:
+    - pytest
+
+# ── Feature flags (optional) ─────────────────────────────────────────────────
+# Remove this section if you do not use feature flags.
+flag_file: ~/.lanegate/feature_flags.json
+
+# ── Deployment pipeline (optional) ───────────────────────────────────────────
+# Remove this section for projects with no deployment pipeline (libraries,
+# research, open-source). Add one entry per environment in promotion order.
+environments:
+  - name: staging
+    branch: staging
+    from: main                          # base branch for pending-diff + promotion
+    trigger: manual                     # manual | auto (auto = hook-driven, lanegate reports only)
+    sync: ff-only                       # ff-only | merge-no-ff
+    guard_script: null                  # path to script; exit 1 blocks promote
+    pre_promote: []                     # scripts to run before promote
+    post_promote: []                    # scripts to run after promote
+    flag_file: ~/.lanegate/staging.feature_flags.json
+
+  - name: production
+    branch: production
+    from: main
+    trigger: manual
+    sync: ff-only
+    guard_script: null
+    pre_promote: []
+    post_promote: []
+    flag_file: ~/.lanegate/feature_flags.json

lanegate-1.0.0/CHANGELOG.md

@@ -0,0 +1,42 @@
+# Changelog
+
+All notable changes to LaneGate are logged here. Dates are the day a change merged to `main`.
+
+## v1.0.0 (2026-08-03) — first public release
+
+### Renamed from Vyuha to LaneGate
+
+The project was renamed to LaneGate before this release (TICK-384/385) after a direct
+domain/naming conflict with an unrelated company. The Python package is now `lanegate`,
+the CLI is `lanegate` (short alias `lgt`), and the config filename/state directory follow
+from that (`.lanegate.yml`, `.lanegate/`). If you have an existing repo initialized with
+an older `vyuha` install, see `docs/migration-vyuha-to-lanegate.md` for the one-time
+manual move.
+
+### Defaults changed from earlier development
+
+Two behaviors that used to require opt-in are now the default for new `lanegate init`
+projects:
+
+- **Independent review by default.** Review no longer silently self-reviews; it runs a
+  genuinely separate reviewer (a different tool instance, a different model, or a
+  different account, in that preference order) before falling back to self-review only
+  when nothing else is available.
+- **Ticket evidence is git-tracked by default.** Ticket files land under version control
+  out of the box instead of being gitignored, so ticket history survives the same way
+  the rest of the repo's history does.
+
+### Known gaps not yet run — read before relying on this release
+
+This release has **not** had the following checks run against it. They don't block
+day-to-day use, but you should know they're outstanding rather than assume full coverage:
+
+- **No `mypy` pass has been run against the tree** (tracked as TICK-365, deferred to v1.6).
+- **No systematic sweep for drifted duplicate logic has been run.** A handful of instances
+  were found incidentally during development and fixed as they were found, but a
+  deliberate grep-driven sweep across module boundaries has not happened (tracked as
+  TICK-366, deferred to v1.6, and should run *before* 365).
+
+A few smaller items are also explicitly deferred to v1.6 and tracked as open tickets
+(TICK-378, TICK-379, TICK-383) — none are launch blockers, all are pre-existing scope
+decisions, not omissions discovered late.

lanegate-1.0.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 Sudheer Donaboina (github.com/sudheerdvn)
+
+   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.

lanegate-1.0.0/NOTICE

@@ -0,0 +1,14 @@
+LaneGate
+Copyright 2026 Sudheer Donaboina (github.com/sudheerdvn)
+
+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.