@harnessforce/claude-code-plugin 0.0.0-bootstrap.0 → 0.1.0

package/.claude-plugin/plugin.json

@@ -0,0 +1,11 @@
+{
+  "name": "harnessforce",
+  "version": "0.1.0",
+  "description": "Harnessforce plugin for Claude Code",
+  "author": {
+    "name": "Lambda Script"
+  },
+  "homepage": "https://github.com/lambda-script/harnessforce-agent",
+  "repository": "https://github.com/lambda-script/harnessforce-agent",
+  "license": "Apache-2.0"
+}

package/.mcp.json

@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "harnessforce": {
+      "type": "http",
+      "url": "${HARNESSFORCE_URL:-https://harnessforce.dev}/mcp"
+    }
+  }
+}

package/LICENSE

@@ -0,0 +1,201 @@
+                                 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 [yyyy] [name of copyright owner]
+
+   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.

package/README.md

@@ -0,0 +1,123 @@
+# harnessforce plugin for Claude Code
+
+The `harnessforce` Claude Code plugin links your Claude Code sessions to
+[Harnessforce](https://github.com/lambda-script/harnessforce-agent) Issues. It is distributed through
+the `harnessforce-agent` marketplace in this repository and as the npm package
+`@harnessforce/claude-code-plugin`, which holds the plugin built against the production connection URL
+and does not bundle the CLI (`/harnessforce:setup` installs `@harnessforce/cli` from npm).
+
+## What it contains
+
+| Part | Purpose |
+| --- | --- |
+| `SessionStart` and `UserPromptSubmit` hooks | Register each session and its config snapshot with Harnessforce |
+| `PostToolUse`, `PostToolUseFailure`, `UserPromptExpansion`, `PermissionRequest`, `PostCompact` and `SessionEnd` hooks | Count the configured skills, commands, subagents and MCP servers a session uses, and send the session usage summary |
+| MCP server `harnessforce` (`<connection URL>/mcp`, HTTP) | Tools to start a run, read an Issue, and record plans, decisions and the Definition of Done |
+| Skill `using-harnessforce` | What Harnessforce records and does not collect, which hook sends what, and when to use the other skills. The `SessionStart` hook injects its body into the context of every session (the build embeds the same text into the hook and the CLI) |
+| Skill `record-run` | Tells the agent when to call those tools |
+| Command `/harnessforce:setup` | Checks Node.js, installs the `harnessforce` CLI, asks whether to send content, runs `harnessforce init` (`--send-content` when chosen) and `harnessforce import`, offers (unchecked by default) to share your usage limits with `harnessforce usage-limits on --yes`, and confirms the first event after a restart |
+| Command `/harnessforce:tune` | Tells you that the agent reads parts of your transcripts through your model provider, runs `harnessforce tune --json`, shows the analysis and the before and after of earlier applied proposals, and makes proposals for the targets with enough data |
+| Skill `propose-improvements` | How the agent writes a proposal (evidence, diff or pull request draft, expected effect, how to measure), keeps permissions minimal and loops bounded, and records it with `harnessforce tune record` before showing it |
+
+The hooks and the MCP server exist only in the build output, because their scripts and connection URL
+come from the build. The copy of the plugin in this repository has no hooks and no MCP server. See
+[Building the local marketplace](../../docs/runbooks/local-marketplace.md).
+
+## Install
+
+Public distribution starts once the production domain of Harnessforce is decided. After that:
+
+```text
+/plugin marketplace add lambda-script/harnessforce-agent
+/plugin install harnessforce@harnessforce-agent
+/harnessforce:setup
+```
+
+Until then, install the [local marketplace build](../../docs/runbooks/local-marketplace.md).
+
+## Requirements
+
+Node.js 18 or later on `PATH`. Without it, Claude Code shows a non-blocking `hook error` and the session
+continues without sending anything.
+
+## Warnings
+
+When a hook cannot send, it shows one line in the session instead of staying silent: Node.js older than 18,
+a failed restart of the hook process, sending not set up (`/harnessforce:setup`), an endpoint that is set
+but not allowed, and a session registration that failed with anything other than 401. The line appears
+only at a session start that registers (`startup`, `clear`, `fork`), except for the two startup failures,
+which appear at every session start. A missing key while `HARNESSFORCE_WORKSPACE_ID` is set shows nothing.
+
+## Session registration hooks
+
+The `harnessforce` plugin registers each Claude Code session with Harnessforce so that runs can be
+linked to issues. On `SessionStart` (`startup`, `clear`, `fork`) it sends the session ID and the git
+repository, branch and commit of `cwd` to `POST <HARNESSFORCE_ENDPOINT>/v1/sessions`. On the first
+prompt it sends the same registration again with the prompt ID. Prompts, responses and file
+contents are never sent.
+
+- For an organization, set `HARNESSFORCE_ENDPOINT` (the ingest base URL; `https:`, or `http:` only
+  for `localhost`, `127.0.0.1` and `[::1]`) and `HARNESSFORCE_INGEST_KEY` (a Workspace ingest key) in
+  the `env` of the managed settings file (`managed-settings.json` or `managed-settings.d/*.json` in
+  the managed directory). The hook reads the Workspace key and its endpoint only from those files,
+  never from the process environment, because a repository's `.claude/settings.json` can set
+  environment variables. Values distributed through MDM or server-managed settings are not read.
+  Hooks do not receive `OTEL_*` variables, so these are separate.
+- Without a managed Workspace key, the hook sends to `HARNESSFORCE_ENDPOINT` from the environment with
+  the user ingest key that `harnessforce init` stored for
+  `HARNESSFORCE_WORKSPACE_ID`, reading it by running `harnessforce otel-headers` from `PATH` (1 second limit).
+  With a user key and `HARNESSFORCE_ISSUE` (set by `harnessforce run`), the registration claims `source=cli`
+  with that issue identifier. A Workspace key never claims `source=cli`.
+- Requires Node.js 18 or later on `PATH`. The hook always exits 0: outside a git repository, without
+  configuration, on errors, or after 2 seconds it gives up quietly and writes the reason to stderr
+  (Claude Code's debug log). Without Node.js, Claude Code shows a non-blocking `hook error`.
+- If the key is revoked, Claude Code shows once per session:
+  組織の送信キーが失効しています。Workspaceの管理者に連絡してください (Workspace key) or
+  送信キーが失効しています。`harnessforce init`を実行してください (user key)
+
+## Config snapshot
+
+At the same `SessionStart`, the hook also sends a config snapshot to
+`POST <HARNESSFORCE_ENDPOINT>/v1/config-snapshots`, including outside a git repository. The snapshot
+describes the agent configuration as a list of components. Each component has a kind, a scope and
+an identifier, plus a SHA-256 hash:
+
+- CLAUDE.md files and rules, skills, agents, commands and workflows, from the managed directory,
+  `~/.claude` and the repository root.
+- `hooks`, `permissions` and `model` from each settings file.
+- MCP servers from `.mcp.json`, `~/.claude.json` and `managed-mcp.json`.
+- The same kinds of component from enabled marketplace plugins in the plugin cache.
+
+File contents, settings values and MCP server configuration (URLs, headers, environment) are never
+sent, only their hashes. Nothing is sent when there are no components, and the snapshot is skipped
+when collection takes over 1 second or finds more than 1,000 components. The collector lives in
+`packages/agent-core/src/config`, shared with `harnessforce run` so it can compute the same snapshot ID.
+
+## Session usage summary
+
+The hooks count, per session, the calls and failures of skills (started through the Skill tool),
+commands (typed by you), subagents (started through the Agent tool) and MCP servers, plus permission
+requests and compactions, and send one summary per session to
+`POST <HARNESSFORCE_ENDPOINT>/v1/session-usage`. Claude Code's telemetry hides the names of your own
+skills, commands, subagents and MCP servers, and the setting that reveals them also sends Bash
+commands and file paths, so the hooks count the names themselves.
+
+- Only names that are identifiers in the session's config snapshot are sent; other calls, such as
+  built-in subagents, are added to an `other` count. Each list keeps the 200 most called names. Prompts,
+  command arguments, tool inputs and results, error messages, compaction summaries and file paths are
+  never read into the record or sent. The MCP tool name is reduced to its server.
+- The record lives in `${CLAUDE_PLUGIN_DATA}/usage/`: `<session_id>.jsonl` holds one line per counted
+  call (time, prompt ID, kind, identifier, failure) and `<session_id>.json` holds the Workspace, the
+  session's identifiers and how much of the record was sent. `SessionStart` creates them when it has a
+  destination and a key, and removes files unchanged for 30 days, up to 100 at a time.
+- With a Workspace key from managed settings, `SessionEnd` sends the summary within 1 second of its
+  start, without running `harnessforce otel-headers`, because Claude Code gives all `SessionEnd` hooks 1.5 seconds
+  together. With a user key, or when that send fails, the next `SessionStart` sends up to 20 summaries of
+  other sessions of the same Workspace whose record has not changed for 10 minutes, oldest first.
+- The counting hooks run asynchronously and never delay the agent. Failures are written to stderr as
+  `harnessforce: session usage failed (<reason>)`; a `401` at `SessionStart` shows the revoked-key
+  notice like the registration does.
+
+## License
+
+[Apache-2.0](../../LICENSE)

package/commands/setup.md

@@ -0,0 +1,83 @@
+---
+description: Harnessforceのsetup。Node.jsの確認、本文データを送るかの選択、CLIの導入、harnessforce init、過去のsessionの取り込み、利用枠を共有するかの選択、再起動後の最初のイベントの確認までを対話で進める
+disable-model-invocation: true
+---
+
+# Harnessforceのsetup
+
+次の手順を順に、利用者と対話しながら進める。commandが失敗したら、その出力を利用者へ示し、以降の手順へ進まずに止まる。
+
+## 1. Node.jsを確かめる
+
+最初に`node --version`を実行する。commandが見つからない、またはversionが18未満なら、CLIの導入へ進まずに次の文言をそのまま表示して終わる。
+
+> プラグインのフックにはNode.js 18以上が必要です。Node.jsを導入してからClaude Codeを再起動し、もう一度`/harnessforce:setup`を実行してください
+
+## 2. 再起動後の実行かを確かめる
+
+`harnessforce --version`が成功し、かつこのsessionの環境変数`HARNESSFORCE_WORKSPACE_ID`が空でなければ、`harnessforce init`の後に再起動したsessionである。手順3から8を行わずに手順9へ進む。
+
+## 3. CLIを導入する
+
+次を実行し、続けて`harnessforce --version`で導入できたことを確かめる。
+
+```sh
+npm install -g @harnessforce/cli
+```
+
+## 4. 本文データを送るかを選ぶ
+
+`harnessforce init`の前に、本文データを送る設定の選択肢を、既定では選ばれない状態で利用者に示す。この時点ではログインが済んでおらず、接続するWorkspaceもそのopt-inの状態も分からないため、opt-inの有無で表示を変えない。
+
+選択肢には次を併せて示す。
+
+- 選ぶと、agentに入力した指示（prompt）の本文がこのWorkspaceへ届き、secretのパターンとメールアドレス・電話番号を`[REDACTED:種類]`に置き換えたうえで保存され、本文データの保持期間（最大30日）で削除される。パターンに一致しない秘密値と個人情報は伏せ字にならず、すべてを検出できるとは限らない。保存した本文は、Workspaceのメンバーの中では送った本人だけが読め、OwnerとAdminも読めない。本人は「自分のやり方」でいつでも自分の本文を削除できる。
+- 本文が保存されるのは、端末のこの設定とWorkspaceのopt-inの2つがそろう場合だけ。Workspaceのopt-inを解除すると、それ以降の本文は受信時に破棄され、既存の本文データも読めなくなる。この設定はモデルの応答やツールの入出力を送る設定を有効にしない。
+- 選んだ場合は`harnessforce init --send-content`、選ばない場合は`harnessforce init`を実行する（手順5）。この設定はClaude Codeのuser settingsの`env`に書き、project（`.claude/settings.json`）とlocal（`.claude/settings.local.json`）の`env`には書かない。その2つのfileの`env`では本文の変数が無視されるため。
+- 選んだ後で止めるときは、user settingsの`env`の`OTEL_LOG_USER_PROMPTS`を`0`にする。止める値はprojectとlocalの`env`でも効く。
+
+選択肢の文言は次をそのまま使う。
+
+> 入力した指示の本文を送って分析に使えます（既定では無効。Workspaceが指示本文をオプトインしている場合だけ有効になります）。有効にすると、エージェントに入力した指示の本文がこのWorkspaceへ届き、保存されます。パターンに一致した秘密値と個人情報は`[REDACTED:種類]`に置き換えますが、すべてを検出できるとは限りません。本文データの保持期間（最大30日）で削除し、Workspaceのメンバーの中では、読めるのは送ったあなただけです。自分のやり方の画面からいつでも削除できます。有効にしますか？
+>
+> You can send the prompts you type for analysis (off by default; it takes effect only if the workspace has opted in to prompts you typed). If enabled, the prompts you type to the agent are delivered to this workspace and stored. Values that match known patterns for secrets and personal information are replaced with `[REDACTED:kind]`, but not everything can be detected. Content is deleted after the content retention period (at most 30 days), and within the workspace only you can read it. You can delete it at any time from My practices. Enable this?
+>
+> 本文を送りません（既定）。後から設定できます
+>
+> Content is not sent (by default). You can enable it later.
+
+## 5. Harnessforceに接続する
+
+手順4の選択に従い、選んだ場合は`harnessforce init --send-content`、選ばない場合は`harnessforce init`を実行する。ブラウザでHarnessforceにログインし、接続するWorkspaceを1つ選ぶよう利用者へ伝える。ブラウザが開かなければ、`harnessforce init`が表示するURLを利用者へ示す。ログインの完了を最大5分待つため、Bashのtimeoutを10分にして実行する。
+
+opt-inしていないWorkspaceでは`harnessforce init --send-content`は本文の設定を書かず、その旨とWorkspaceの設定のデータの保持への案内を表示して終了コード0で終わる。失敗として扱わず、表示された文言をそのまま利用者へ示す。
+
+## 6. 過去のsessionを取り込む
+
+`harnessforce import`を実行し、送信した件数と読み飛ばした件数を利用者へ伝える。
+
+## 7. 利用枠を共有するかを選ぶ
+
+`harnessforce init`の後に、`harnessforce usage-limits status`を実行する。表示のWorkspaceのopt-inが「有効」でなければ（「無効」「確認できません」を含む）、利用枠の選択肢を示さず手順8へ進む。「有効」なら、利用枠（Claude Codeの5時間と7日の枠の使用率とリセット時刻）をこのWorkspaceのメンバーと共有する選択肢を、既定では選ばれない状態で利用者に示す。選ばれなければ、何も実行せず手順8へ進む。
+
+選択肢の文言は次をそのまま使う。
+
+> 利用枠を共有できます（既定では共有しません）。共有すると、あなたの名前とともに、あなたの利用枠（5時間・7日などの窓の使用率とリセット時刻だけ）を、このWorkspaceのメンバー全員が見られます。プロンプトなどの本文は送りません。いつでもやめられ、やめると保存済みの値も削除します。メンバーの順位づけには使いません。共有しますか？
+>
+> You can share your usage limits (not shared by default). If shared, everyone in this workspace can see your usage limits together with your name (only the usage percentage and reset time of each window, such as 5 hours and 7 days). No prompt or other content is sent. You can stop at any time, and stopping deletes the stored values. They are not used to rank members. Share them?
+>
+> 共有しません（既定）。後から`harnessforce usage-limits on`で設定できます
+>
+> Not shared (by default). You can set it up later with `harnessforce usage-limits on`.
+
+共有を選んだ場合だけ、利用者自身が同意の文面に答えるため、`!harnessforce usage-limits on`を利用者に入力してもらう。`--yes`は付けず、agentが同意を代行しない。同意の文面に`y`と答えると、既にstatusLineを使っている場合（claude-hudなど）は、そのcommandを包んで表示と終了コードを変えずに残す。Windowsや、組み込めないstatusLineでは、このcommandは何も変えずに理由を表示して0以外で終わる。その表示を利用者へそのまま示し、他の手順は続ける。やめるときは`harnessforce usage-limits off`を案内する。
+
+## 8. 再起動を案内する
+
+次を利用者へ伝えて終わる。
+
+> Claude Codeを再起動すると設定が反映されます。再起動したsessionで、もう一度`/harnessforce:setup`を実行してください。最初のイベントが届いたかを確認します。
+
+## 9. 最初のイベントを確認する
+
+このsessionの開始時に、pluginのhookがsessionをHarnessforceへ送っている。利用者に、ブラウザでHarnessforceのHome（環境変数`HARNESSFORCE_URL`のURL）を開き、最初のRunの待機画面で受信を確認するよう伝える。15分待っても届かなければ、待機画面が示す原因ごとの確認手順に沿って確かめるよう伝える。

package/commands/tune.md

@@ -0,0 +1,39 @@
+---
+description: 自分の過去のsessionを分析し、分析結果、前回の提案の前後と、人の介入、ループにできる繰り返し、MCP server、使い方の改善の提案を表示する。ファイルは書き換えない
+argument-hint: "[--all] [--no-send]"
+disable-model-invocation: true
+---
+
+# 過去のsessionの分析と改善の提案
+
+次の手順を順に進める。この実行では、利用者のファイル、設定、repository、managed settingsを書き換えない。書き込むのは`harnessforce tune`と`harnessforce tune record`が`~/.harnessforce/tune/`へ書くものだけである。
+
+## 1. modelのproviderへ渡ることを伝える
+
+何かを実行する前に、次の文言をそのまま表示する。
+
+> この実行では、提案を作るために、この端末のsessionの記録の一部をagentが読みます。読んだ内容は、ふだんこのagentに使っているmodelのproviderへ、通常のsessionと同じ経路で渡ります。Harnessforceへは渡りません。Harnessforceへ送るのは、公開の規則で数えた分析結果の値だけです。
+
+## 2. 分析する
+
+次を実行する。`harnessforce tune --json`を起動し、分析結果と、提案を作る条件を対象ごとに判定した結果を表示する。送信と未送信の分の再送を含むため、Bashのtimeoutを10分にする。
+
+```sh
+node "${CLAUDE_PLUGIN_ROOT}/skills/propose-improvements/scripts/summarize.mjs" $ARGUMENTS
+```
+
+- stderrの行は`harnessforce tune`の文言である。省略も言い換えもせずに、すべてそのまま表示する。
+- stdoutの分析結果（人の介入、ループにできる繰り返し、MCP server、使い方）をそのまま表示する。「未計測」を0と言い換えない。使い方は端末だけの値であり、Harnessforceへ送られない。
+- 「前回の提案の前後」の行があれば、新しい提案の前に「前回の提案の前後」としてそのまま表示し、「前後の差（因果を示しません）」と「起点は適用を検出した時刻です」を省略しない。「比較データなし」を差0と言い換えない。
+- 終了コードが0と3以外なら、提案を作らずに終わる。`harnessforce`が見つからない旨の文言が出た場合も同じである。
+- 「データ不足のため提案を作りません」の行があれば、その行を表示し、提案を作らずに終わる。
+
+## 3. 提案を作る
+
+「提案の対象」の行をすべて表示する。「データ不足」と「未計測のため提案しません」の行は、あと何が必要かを含めてそのまま表示し、その対象の提案を作らない。
+
+「提案を作れます」の対象について、このpluginの`propose-improvements`のskillの手順に従って提案を作り、`harnessforce tune record`で記録してから表示する。記録が終了コード0で終わらなかった提案は表示しない。
+
+## 4. 適用の仕方を伝える
+
+最後に、提案の適用は利用者が行うことを伝える。手で編集する、`git apply`する、自分のsessionでagentに適用を指示する、のいずれかで適用する。このcommandは適用しない。適用した提案は、次の`/harnessforce:tune`の実行で検出され、件数だけがHarnessforceへ送られる。

package/hooks/hooks.json

@@ -0,0 +1,127 @@
+{
+  "description": "Register Claude Code sessions with Harnessforce and send their usage summaries",
+  "hooks": {
+    "SessionStart": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node",
+            "args": [
+              "${CLAUDE_PLUGIN_ROOT}/scripts/harnessforce-hook.cjs",
+              "session-start"
+            ],
+            "timeout": 10
+          }
+        ]
+      }
+    ],
+    "UserPromptSubmit": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node",
+            "args": [
+              "${CLAUDE_PLUGIN_ROOT}/scripts/harnessforce-hook.cjs",
+              "user-prompt-submit"
+            ],
+            "timeout": 10
+          }
+        ]
+      }
+    ],
+    "SessionEnd": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node",
+            "args": [
+              "${CLAUDE_PLUGIN_ROOT}/scripts/harnessforce-hook.cjs",
+              "session-end"
+            ],
+            "timeout": 10
+          }
+        ]
+      }
+    ],
+    "PostToolUse": [
+      {
+        "matcher": "^(Skill|Agent|Task)$|^mcp__",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node",
+            "args": [
+              "${CLAUDE_PLUGIN_ROOT}/scripts/harnessforce-hook.cjs",
+              "post-tool-use"
+            ],
+            "async": true
+          }
+        ]
+      }
+    ],
+    "PostToolUseFailure": [
+      {
+        "matcher": "^(Skill|Agent|Task)$|^mcp__",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node",
+            "args": [
+              "${CLAUDE_PLUGIN_ROOT}/scripts/harnessforce-hook.cjs",
+              "post-tool-use-failure"
+            ],
+            "async": true
+          }
+        ]
+      }
+    ],
+    "UserPromptExpansion": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node",
+            "args": [
+              "${CLAUDE_PLUGIN_ROOT}/scripts/harnessforce-hook.cjs",
+              "user-prompt-expansion"
+            ],
+            "async": true
+          }
+        ]
+      }
+    ],
+    "PermissionRequest": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node",
+            "args": [
+              "${CLAUDE_PLUGIN_ROOT}/scripts/harnessforce-hook.cjs",
+              "permission-request"
+            ],
+            "async": true
+          }
+        ]
+      }
+    ],
+    "PostCompact": [
+      {
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node",
+            "args": [
+              "${CLAUDE_PLUGIN_ROOT}/scripts/harnessforce-hook.cjs",
+              "post-compact"
+            ],
+            "async": true
+          }
+        ]
+      }
+    ]
+  }
+}

package/package.json

@@ -1,11 +1,29 @@
 {
   "name": "@harnessforce/claude-code-plugin",
-  "version": "0.0.0-bootstrap.0",
-  "description": "Placeholder to attach npm trusted publishing. Not for use.",
+  "version": "0.1.0",
+  "description": "Harnessforce plugin for Claude Code",
+  "keywords": [
+    "harnessforce",
+    "claude-code",
+    "claude-code-plugin",
+    "opentelemetry",
+    "ai-agents"
+  ],
   "license": "Apache-2.0",
+  "homepage": "https://github.com/lambda-script/harnessforce-agent/tree/main/plugins/harnessforce#readme",
+  "bugs": {
+    "url": "https://github.com/lambda-script/harnessforce-agent/issues"
+  },
   "repository": {
     "type": "git",
     "url": "git+https://github.com/lambda-script/harnessforce-agent.git",
     "directory": "plugins/harnessforce"
+  },
+  "publishConfig": {
+    "access": "public",
+    "provenance": true
+  },
+  "engines": {
+    "node": ">=18"
   }
-}
+}