Rename package to scoped @valknar/triggershell

Matches vpinball-wasm's move back to a scoped name: an unscoped
package on this Gitea npm registry can't be mapped via a normal
`.npmrc` `@scope:registry=` entry, since the registry doesn't proxy
npmjs.org. Scoping lets any consumer add one registry line instead of
pinning a tarball URL per dependency.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012hQoM3jJT1Lx7CMTciMzvD

README.md

@@ -24,7 +24,7 @@ API for automation.
 ## Quickstart
 
 ```bash
-npm install -g triggershell      # or: npx triggershell <command> for one-off use
+npm install -g @valknar/triggershell   # or: npx @valknar/triggershell <command> for one-off use
 triggershell init                # scaffold triggershell.yml (+ .env for secrets) in the current directory
 triggershell users add admin     # create a login (skip if you set auth.enabled: false)
 triggershell start               # start the app and open the browser
@@ -113,7 +113,7 @@ the script — always as a discrete argv element or env var, never interpolated
 | `triggershell service install [--system]`                                                     | Install a systemd unit that runs `triggershell start` (per-user by default, Linux only)                                                                                                                                |
 | `triggershell service uninstall [--system]`                                                   | Stop, disable, and remove the systemd unit                                                                                                                                                                             |
 | `triggershell service status [--system]`                                                      | Show the systemd unit's status                                                                                                                                                                                         |
-| `triggershell service logs [-n LINES] [--no-follow] [--system]`                               | Tail the systemd unit's logs (wraps `journalctl`)                                                                                                                                                                      |
+| `triggershell service logs [-n LINES] [--no-follow] [--system]`                               | Tail the systemd unit's logs (wraps `journalctl -o cat`, so each line is raw JSON - pipe through `jq` for pretty-printing)                                                                                             |
 
 ### Running scripts from the CLI
 

docs/ARCHITECTURE.md

@@ -76,7 +76,9 @@ targets `/etc/systemd/system/` instead and prints the `sudo` commands to run if
 explicit `systemctl --user enable --now triggershell`, since it's the point where the service
 actually starts listening and running scripts. `triggershell service status`/`uninstall`/`logs` are
 thin wrappers around `systemctl`/`journalctl` respectively - no unit-file parsing or log storage of
-our own, journald already does that.
+our own, journald already does that. `logs` passes `-o cat` so each line is the raw pino JSON
+payload rather than journalctl's own timestamp/hostname/unit prefix - pipeable straight into `jq`
+for pretty-printing without pulling `pino-pretty` into the CLI's runtime dependencies.
 
 ## Cross-module-graph state
 

package.json

@@ -1,6 +1,6 @@
 {
-  "name": "triggershell",
+  "name": "@valknar/triggershell",
-  "version": "1.0.4",
+  "version": "1.2.0",
   "license": "MIT",
   "type": "module",
   "repository": {

src/cli/commands/service.ts

@@ -137,7 +137,9 @@ export async function serviceLogsCommand(
 ): Promise<void> {
   const scope = scopeOf(opts);
   const args = scope === "user" ? ["--user"] : [];
-  args.push("-u", SERVICE_NAME);
+  // -o cat strips journalctl's own prefix (timestamp/hostname/unit) so each line is the raw pino
+  // JSON payload - pipeable straight into `jq` or similar without journalctl's wrapper in the way.
+  args.push("-u", SERVICE_NAME, "-o", "cat");
   if (opts.follow !== false) args.push("-f");
   if (opts.lines !== undefined) args.push("-n", String(opts.lines));
 

src/cli/index.ts

@@ -184,10 +184,8 @@ service
 service
   .command("logs")
   .description("Tail the systemd unit's logs (journalctl).")
-  .option(
+  .option("-n, --lines <n>", "Number of recent log lines to show.", (v) =>
-    "-n, --lines <n>",
+    Number(v),
-    "Number of recent log lines to show.",
-    (v) => Number(v),
   )
   .option(
     "--no-follow",