lshed 0.16.0 → 0.16.1

package/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog
 
+## 0.16.1 — 2026-09-09
+
+- `lshed report --open` on Windows went through `cmd /c start`, which cuts the URL at its first `&` and expands `%…%` sequences, so the issue form would have opened without the summary. It now hands PowerShell an encoded command, which parses nothing. On Linux without `xdg-open` (WSL, most servers) `wslview` is tried next, and `lshed report --url` prints the prefilled link for a machine with no browser at all. On Windows the report also hides the profile folder when a path spells it with an 8.3 short name (`C:\Users\RUNNER~1\…` for `runneradmin`, which is how `TEMP` usually reads), by treating any `<drive>:\Users\<name>` on the home drive as `~`. The smoke suite, which CI runs on Ubuntu, macOS and Windows, now runs `report` and checks that no user directory appears in its output in any spelling.
+
 ## 0.16.0 — 2026-09-09
 
 - New `lshed report`: prints what a bug report needs and nothing else — lshed version and runtime, OS, the agent and its root, the agent CLI's version, the applied profile as numbers, and the names (not contents) of what the shed holds. Home directories show as `~`; no environment value, setting or shed file is included. `--open` puts the same text into the repository's issue form. After a failed command, in a terminal, lshed asks once whether to open that form; the default is no, `LSHED_REPORT=0` removes the question, and outside a terminal only a one-line hint is printed. lshed sends nothing by itself in any of these paths — it opens the browser on a URL and the user decides whether to submit.

package/README.ko.md

@@ -474,7 +474,7 @@ lshed list [--unused]                           창고의 내용과 그것을
 lshed remove <key>                              창고에서 부품이나 패키지 삭제
 lshed prune [--yes]                             어느 프로필도 안 쓰는 것 전부 삭제
 lshed scan                                      루트를 읽기만 하고 나열
-lshed report [--open]                           이슈에 붙여 넣을 이 설정의 요약, --open 은 GitHub 이슈 폼에 채워서 연다
+lshed report [--open | --url]                   이슈에 붙여 넣을 이 설정의 요약, --open 은 GitHub 이슈 폼에 채워서 열고 --url 은 그 링크만 찍는다
 ```
 
 키는 `카테고리/id`이고, 모호하지 않으면 `id`만 써도 됩니다: `skills/paper-review`, `mcp/exa`, `packages/gstack`. id는 에이전트가 읽는 파일·디렉터리 이름 그대로이며 어느 문자 체계든 됩니다(`skills/논문리뷰`). 글자, 숫자, `.`, `_`, `-`, 그리고 하위 폴더에 둔 에이전트·명령을 위한 구간 사이 `/`가 허용됩니다.
@@ -545,7 +545,7 @@ lshed report [--open]                           이슈에 붙여 넣을 이 설
 
 ## 문제 해결
 
-- **다른 문제가 생겼다** — `lshed report` 가 버그 보고에 필요한 요약을 찍습니다(비밀은 없지만 직접 확인하세요). `lshed report --open` 은 그것을 새 이슈 폼에 채워 엽니다. 명령이 실패한 직후에도 같은 것을 묻는데, 아니오라고 하거나 `LSHED_REPORT=0` 을 두면 아무 일도 없습니다.
+- **다른 문제가 생겼다** — `lshed report` 가 버그 보고에 필요한 요약을 찍습니다(비밀은 없지만 직접 확인하세요). `lshed report --open` 은 그것을 새 이슈 폼에 채워 엽니다(브라우저가 없는 기기에서는 `--url` 이 링크만 찍습니다). 명령이 실패한 직후에도 같은 것을 묻는데, 아니오라고 하거나 `LSHED_REPORT=0` 을 두면 아무 일도 없습니다.
 - **"Shed location unknown. Pass --shed <dir> or set LSHED_HOME."** (창고 위치를 모름) — `--shed <dir>`를 주거나 `LSHED_HOME`을 설정하세요. `restore`가 한 번 성공하면 기억합니다.
 - **restore가 내 `CLAUDE.md`를 바꿨다** — `~/.claude/lshed/backups/<시각>/CLAUDE.md`에 있습니다. 내용을 창고의 조각으로 옮기고 그 조각을 프로필에 넣으세요.
 - **로컬에서 고친 스킬을 지키고 싶다** — `lshed diff`로 보고, `lshed save <id>`로 창고에 넣고, `lshed sync`.

package/README.md

@@ -474,7 +474,7 @@ lshed list [--unused]                           what is in the shed, and which p
 lshed remove <key>                              drop a component or package from the shed
 lshed prune [--yes]                             drop everything no profile uses
 lshed scan                                      list what the agent root holds, without writing anything
-lshed report [--open]                           summary of this setup to paste into an issue; --open prefills one on GitHub
+lshed report [--open | --url]                   summary of this setup to paste into an issue; --open prefills one on GitHub, --url prints that link
 ```
 
 Keys are `category/id`, or just `id` when unambiguous: `skills/paper-review`, `mcp/exa`, `packages/gstack`. An id is the file or directory name the agent reads, in any script (`skills/논문리뷰` is fine); letters, digits, `.`, `_` and `-` are allowed, and `/` between segments for nested agents and commands.
@@ -545,7 +545,7 @@ The shed is the source of truth for authored parts: `save` copies local edits ba
 
 ## Troubleshooting
 
-- **Something else went wrong** — `lshed report` prints the summary a bug report needs (nothing secret; check it yourself), `lshed report --open` puts it into a new issue form. The same question is asked right after a failed command; answer no, or set `LSHED_REPORT=0`, and nothing happens.
+- **Something else went wrong** — `lshed report` prints the summary a bug report needs (nothing secret; check it yourself), `lshed report --open` puts it into a new issue form (`--url` prints the link instead, for a machine without a browser). The same question is asked right after a failed command; answer no, or set `LSHED_REPORT=0`, and nothing happens.
 - **"Shed location unknown. Pass --shed <dir> or set LSHED_HOME."** — do one of those. After one successful `restore`, lshed remembers it.
 - **restore replaced my `CLAUDE.md`** — it is in `~/.claude/lshed/backups/<timestamp>/CLAUDE.md`. Move its content into a fragment in the shed and add that fragment to your profile.
 - **I edited a skill locally and want to keep it** — `lshed diff` to see, `lshed save <id>` to push it into the shed, then `lshed sync`.