dsh-rules

LIMITATIONS

Known limitations

- Only files **inside the project root** can activate rules; reads outside the root never trigger (avoids `../` false positives). - The touched-path set is in-memory: after resuming a session, rules re-activate as the agent re-reads files (the previously matched list is restored from the log). - Deployments with `includeRuntimeContext: false` are unaffected — this plugin injects its own message and does not depend on the runtime-context snapshot. - Rules are injected as "superseding snapshot" messages; the session log retains historical snapshots, but each snapshot is the complete current set and the model follows the latest one. - A snapshot's `matched files` list is a record of the moment it was rendered: files matched later do not re-send the rules, so that list can lag behind the session. The active set is always the one in the latest snapshot.