mcptask-rails-runner 0.3.25 → 0.3.27

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 9a1f39f18db2975b0962f06663f1fe20a3cac941038509a1f5d5352f41540d46
-  data.tar.gz: bf7960b5caa082e3e94ad980c6529e99dd368b80c863509560654441e50c2460
+  metadata.gz: f753fa3a7050b05b3287867b14c19e8db4a22044c73a9619eb0aa9336e184b3b
+  data.tar.gz: d9101426d33c852f0d6259b10b07c851d5055fbecad2ff05201fd13898ab57aa
 SHA512:
-  metadata.gz: bb9638054f7d91bfadf8f7b35816e2f443990d42a6ecfce51ef3de441a6e09c15da81d85c60b642b7bb063e61913eda9f4bc468ffe56e476b5f6027ca053792b
-  data.tar.gz: 56d8dcb59ac359d454045c1a72cee451aa7dd8b104674858d58aa3baff7c965aeb75717a6f0960ed5806b0d4770e82976c7c47036cf95a3e33de38481deb136a
+  metadata.gz: b5b468957425ecb3159e15b97ab6a5f412ed69550c8eb5c43165e7ab21bf77fe73811c921ccc2d5c752392ca73cb2dfa848dc4a66ee771809ada2500245db561
+  data.tar.gz: 5a78068b18c6a0adfdecfa847e5e35be26116e7f3114f57615c6f4d5caa814de4fa217c8a506b2f2530360db21cfca59dd5e445aa9e2c44792a609d74b700d70

data/CHANGELOG.md

@@ -5,6 +5,77 @@ entries below describe wrapper changes only. Binary changes are listed in the
 [mcptask-releases](https://github.com/jchsoft/mcptask-releases/releases)
 release notes for the same tag.
 
+## 0.3.27
+
+Full binary notes in
+[mcptask-releases v0.3.27](https://github.com/jchsoft/mcptask-releases/releases/tag/v0.3.27).
+
+**Upgrading takes two commands.** `mcptask_runner update --self` replaces the
+binary; then a bare `mcptask_runner update` in any one project on the host,
+because the bundled `pr` skill and the permission baseline both changed. Run it
+while no runner is working that checkout.
+
+Wrapper changes:
+
+- **`mcptask_runner:install` forwards `--cli` and `--git-host`.** Either as
+  rake args — `rake "mcptask_runner:install[--cli codex,--git-host bitbucket]"` —
+  or as `CLI=codex GIT_HOST=bitbucket rake mcptask_runner:install`; env wins on
+  a tie. `update` takes no flags; re-run `install` to change them. A project
+  without a `harness:` line is refused by name, and `mcptask_runner:update`
+  writes `harness: claude` once for a legacy install so it gets through.
+
+Binary changes carried by this version:
+
+- **GitLab is a third git host**, driven through the `glab` CLI, which holds
+  its own login — nothing for the runner to store. gitlab.com is derived from
+  the origin; a self-managed instance sets `git_host: gitlab`. `pr checks`
+  prints one row per merge request because GitLab publishes one pipeline
+  status. Verified in manual and auto-squash mode on a real gitlab.com project
+  (story #12448).
+- **`mcptask_runner` is on the child's PATH on every project.** Until now only
+  projects with this gem could reach it from inside a task, through Bundler's
+  shim; a project without the gem got `exit 127` on every `mcptask_runner pr`
+  call (task #12456).
+- **A failing `gh` or `glab` repeats what the CLI said** instead of a bare
+  `exit status 1` (task #12454).
+- **A machine's own pull-request skill no longer outranks the runner.** The
+  create step now claims the words "create a pull request"; the stale
+  `Skill(pull-request-creator)` approval left the permission baseline
+  (task #12455).
+- **Adoption works on an rbenv, asdf or mise host** — the bundled gem is found
+  through the project's Ruby, not only through `GEM_HOME` (task #12435).
+
+## 0.3.26
+
+No wrapper changes. Full notes in
+[mcptask-releases v0.3.26](https://github.com/jchsoft/mcptask-releases/releases/tag/v0.3.26).
+
+**Upgrading takes two commands again.** `mcptask_runner update --self`
+replaces the binary; then a bare `mcptask_runner update` in any one project on
+the host, because the bundled `pr` skill gained the review commands. Run it
+while no runner is working that checkout.
+
+Binary changes carried by this version:
+
+- **Auto-squash asks the git host whether its checks passed before merging.**
+  `mcptask_runner pr checks <n>` sits between the local `bin/ci` gate and the
+  merge: SUCCESS or NONE merge, FAILED ends `ci_failed` with the PR left open,
+  IN_PROGRESS waits (bounded). A green local gate is no longer permission to
+  merge; `status_detail` in the result marker says which verdict applied
+  (task #12425, found on the real Bitbucket verification of #12365).
+- **The review executors speak `mcptask_runner pr` only.** `pr list --open`
+  and `pr reviews <n>` (verdicts and inline notes, on GitHub and Bitbucket)
+  replaced the last `gh` calls in any prompt the runner composes (task #12420).
+- **`init --home-dir` re-roots the Bitbucket credential** like the mcptask
+  token, and a re-run on a Bitbucket project says whether it left the
+  credential alone and which variables it wanted (task #12424).
+- **Run records say how the attempt ended.** `final_status` in
+  `log/runs/run_*.json` carries the verdict (`success`, `ci_failed`,
+  `merge_unverified`, …) instead of repeating `processing` (task #12426).
+- **A close code the server sent is logged even when the write failure is
+  noticed first**; the reader's account gets its own line when the reconnect
+  notice already went out (task #12421).
+
 ## 0.3.25
 
 No wrapper changes. Full notes in

data/README.md

@@ -31,7 +31,7 @@ with an older one.
 ## Requirements
 
 - Ruby >= 3.0, Rails >= 6.0
-- [Claude Code](https://claude.com/claude-code) CLI
+- One of [Claude Code](https://claude.com/claude-code), [Codex CLI](https://github.com/openai/codex) or [OpenCode](https://opencode.ai), signed in by the machine owner — picked per project at install time (`--cli` below; Codex and OpenCode need their own login on top of the runner account)
 - An mcptask.online account
 
 ## Installation
@@ -71,15 +71,38 @@ keeps working but stops recording what it ran. The regenerated one execs
 Every `rake mcptask_runner:*` invocation and shell alias keeps working
 unchanged. Your existing
 `config/mcptask_runner.yml`, `.mcp.json` and `.claude/` setup are read by the
-Go binary as-is. The only legacy task without a counterpart is
+Go binary as-is — with one exception: a project without a `harness:` line is
+now refused by name (no silent default), and `mcptask_runner:update` will write
+`harness: claude` once for a legacy `.mcp.json`-style install so the host gets
+through the gate on the next run. The only legacy task without a counterpart is
 `mcptask_runner:prepare:permissions` — permission sync is part of
 `mcptask_runner:install` now.
 
+### Picking the coding CLI and the git host
+
+`mcptask_runner:install` delegates to `mcptask_runner init`, which takes the
+harness choice and the git host as flags. Both reach the binary through the
+rake task in two equivalent ways — choose whichever fits how the command is
+invoked:
+
+```bash
+# Square-bracket form — works inside a Procfile or a CI step:
+bundle exec rake "mcptask_runner:install[--cli codex]"
+bundle exec rake "mcptask_runner:install[--cli codex,--git-host bitbucket]"
+
+# Environment form — what an operator types at the shell, where a one-line
+# override (CLI=opencode rake …) is easier than retyping the rake args:
+CLI=codex GIT_HOST=bitbucket bundle exec rake mcptask_runner:install
+```
+
+Env wins on a tie. `update` does not take flags — re-run `install` with the
+ones you want.
+
 ## Tasks
 
 | Task | Delegates to |
 |---|---|
-| `mcptask_runner:install` | `mcptask_runner init` (from `~/.mcptask/bin`) |
+| `mcptask_runner:install` | `mcptask_runner init [--cli <name>] [--git-host <name>]` (from `~/.mcptask/bin`) |
 | `mcptask_runner:update` | `mcptask_runner update` (from `~/.mcptask/bin`) |
 | `mcptask_runner:bug_report` | `mcptask_runner bug-report` |
 | `mcptask_runner:version` | `mcptask_runner version` |

data/lib/mcptask_rails_runner/binary.rb

@@ -132,6 +132,39 @@ module McptaskRailsRunner
       Kernel.exec(install!, *args)
     end
 
+    # Flags `mcptask_runner init` consumes in one form or another, paired with the
+    # env-var name each is read under on the rake side. The dash in `--git-host`
+    # would be stripped by `.delete_prefix` and lost by `.upcase` (`GIT-HOST`
+    # is not what anyone writes), so the substitution is explicit.
+    INIT_FLAGS = {
+      "--cli" => "CLI",
+      "--git-host" => "GIT_HOST"
+    }.freeze
+
+    # Env comes first so it wins on tie: the rake args baked into a Procfile or
+    # a CI step are the ones harder to override, so they are the ones we keep
+    # second and let the developer's shell environment silence.
+    def forwarded_init_flags(rake_args, env = ENV)
+      raw = rake_args.to_a.flat_map { |a| a.to_s.split(",") }.map(&:strip).reject(&:empty?)
+      from_rake = raw.flat_map { |token| token.split(/\s+/) }
+
+      from_env = []
+      INIT_FLAGS.each do |flag, var|
+        value = env[var]
+        from_env << flag << value if value && !value.empty?
+      end
+
+      # Drop rake-side flags the env already answered — env wins on a tie. The
+      # check is on the flag name alone: if `--cli` came from the env, the rake
+      # side's `--cli <value>` (whatever value it carries) is overridden by it.
+      rake_flags = from_env.each_slice(2).map(&:first).to_set
+      remaining_rake = from_rake.each_slice(2).reject do |pair|
+        pair.size == 2 && rake_flags.include?(pair.first)
+      end.flatten
+
+      (from_env + remaining_rake)
+    end
+
     # What the installed copy reports about itself, or nil when there is none —
     # or when it cannot be asked, which a stray file at that path cannot be.
     #

data/lib/mcptask_rails_runner/version.rb

@@ -10,5 +10,5 @@ module McptaskRailsRunner
   # Binary::INSTALL_DIR. So the pin is per project and per foreground rake
   # invocation; the installed copy is per machine, and the newest binary any of
   # those projects offers is the one that stays.
-  VERSION = "0.3.25"
+  VERSION = "0.3.27"
 end

data/lib/tasks/mcptask_runner.rake

@@ -15,9 +15,22 @@
 require "mcptask_rails_runner"
 
 namespace :mcptask_runner do
+  # `init` and `update` take flags the harness choice and git host depend on
+  # (--cli <name>, --git-host <name>). Forward everything the rake caller passed
+  # after the rake args so a Codex/OpenCode or Bitbucket user has a documented
+  # path through the gem:
+  #
+  #   bundle exec rake "mcptask_runner:install[--cli codex]"
+  #   bundle exec rake "mcptask_runner:install[--cli codex,--git-host bitbucket]"
+  #   CLI=codex GIT_HOST=bitbucket bundle exec rake mcptask_runner:install
+  #
+  # Anything else (`update`, the manual/auto tasks) keeps its 1:1 delegation so
+  # a flag the binary does not know about surfaces as a real error from it.
   desc "Install skills, permissions, token and scheduled job into this project"
-  task :install do
-    McptaskRailsRunner::Binary.exec_installed!("init")
+  task :install, [:args] do |_t, args|
+    McptaskRailsRunner::Binary.exec_installed!(
+      "init", *McptaskRailsRunner::Binary.forwarded_init_flags(args, ENV)
+    )
   end
 
   desc "Refresh bundled skills and helpers"

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: mcptask-rails-runner
 version: !ruby/object:Gem::Version
-  version: 0.3.25
+  version: 0.3.27
 platform: ruby
 authors:
 - Josef Chmel
@@ -25,7 +25,9 @@ dependencies:
         version: '6.0'
 description: Thin Rails wrapper around the mcptask_runner Go binary. Ships the platform-specific
   binary inside the gem and exposes the same rake tasks as the legacy mcptask_runner
-  gem, delegating 1:1 to the CLI.
+  gem, delegating 1:1 to the CLI. Drives Claude Code, Codex CLI or OpenCode — pick
+  one with `mcptask_runner:install[--cli <name>]`. Works with GitHub and Bitbucket
+  Cloud repos (`--git-host <name>`).
 email:
 - info@jchsoft.cz
 executables: []
@@ -66,5 +68,6 @@ required_rubygems_version: !ruby/object:Gem::Requirement
 requirements: []
 rubygems_version: 3.6.9
 specification_version: 4
-summary: mcptask.online autonomous runner for Rails apps
+summary: mcptask.online autonomous runner for Rails apps (drives Claude Code, Codex
+  CLI or OpenCode)
 test_files: []