plugin-catalog: update tirith to 0.1.1

plugin-catalog/tirith.yaml

@@ -1,8 +1,8 @@
 name: tirith
 repo: https://github.com/sheeki03/hermes-plugin-tirith
-sha: e6482ffa5df5bafd872c51c71c152a02c27917d8
+sha: 42862b4e49cc5a46985973d982e2bf3969ad724f
 subdir: tirith
-version: "0.1.0"
+version: "0.1.1"
 title: tirith
 description: >-
   Check every terminal command with your installed tirith before it runs: lookalike and homograph
@@ -11,9 +11,9 @@ description: >-
   critical findings are refused, warnings run with the warning added to the result; unattended runs
   follow approvals.*_mode.
   Disclosure — runs the user-installed tirith binary (0.5.0 or later; never downloaded, installed or
-  updated by the plugin) on every terminal command and every line sent to a background terminal, in
-  the command's working directory (on Hermes 0.22.3 and later, see known issues), with the command on
-  stdin; tirith logs each check locally and, unless offline is set, may refresh its signed threat
+  updated by the plugin) on every terminal command and completed shell command sent to a background
+  terminal, in the command's working directory, with the command on stdin; tirith logs each check
+  locally and, unless offline is set, may refresh its signed threat
   database, query OSV.dev, deps.dev and ecosyste.ms, download the CISA KEV feed, and query Google
   Safe Browsing (only with your key); fails closed (asks, or refuses when unattended) if tirith is
   missing, older than 0.5.0, times out or gives no verdict.
@@ -22,22 +22,13 @@ tier: community
 category: tools
 requires_hermes: ">=0.21.5"
 docs_url: https://github.com/sheeki03/hermes-plugin-tirith/blob/main/tirith/README.md
-# The README at the pinned 0.1.0 commit still has pre-release wording; it renders again from the
-# 0.1.1 re-pin.
-readme: false
+readme: true
 platforms: []
 known_issues:
   - >-
     Hermes 0.21.5 still runs a built-in tirith check before plugins; run
     `hermes config set security.tirith_enabled false` so each command is not checked twice.
     Hermes 0.21.6 and later do not have it.
-  - >-
-    On Hermes 0.22.3 and later, plugin hooks run in the gateway process and plugin 0.1.0 does not
-    read the session's working directory. Until a command sets workdir or changes directory, tirith
-    checks it in the gateway's TERMINAL_CWD or own directory, so a project's .tirith/policy.yaml may
-    not apply and the approval prompt may name that directory. Built-in detections, your user and
-    organisation policy, critical refusals and fail-closed behaviour still apply. Fixed in plugin
-    0.1.1.
 capabilities:
   provides_tools: []
   provides_hooks: