@groundtrack/hooks 0.1.15 → 0.1.17

package/dist/session-import/discovery.js

@@ -178,6 +178,7 @@ export function discoverSessions(options) {
             return null;
         return identity.remotes.values().next().value ?? null;
     };
+    const targetRemote = soleRemote(options.repository);
     for (const candidate of discovered.included) {
         const { path, metadata } = candidate;
         const modifiedAtMs = candidate.modifiedAt?.getTime() ??
@@ -202,11 +203,16 @@ export function discoverSessions(options) {
         const normalizedRemote = metadata.repositoryUrl
             ? normalizeRepositoryUrl(metadata.repositoryUrl)
             : null;
-        const cwdMatchesCurrentRepository = Boolean(options.repository && metadata.cwd && isInside(metadata.cwd, options.repository.root));
-        const currentRepositoryRemote = cwdMatchesCurrentRepository
-            ? soleRemote(options.repository)
-            : null;
+        const pathMatchesCurrentRepository = Boolean(options.repository && metadata.cwd && isInside(metadata.cwd, options.repository.root));
         const remoteMatchesCurrentRepository = Boolean(options.repository && normalizedRemote && options.repository.remotes.has(normalizedRemote));
+        // A session may retain an old remote after an owner rename. Its recorded checkout
+        // can still identify the target repository even when importing from another worktree.
+        const checkoutMatchesCurrentRepository = Boolean(targetRemote &&
+            !pathMatchesCurrentRepository &&
+            !remoteMatchesCurrentRepository &&
+            soleRemote(repositoryIdentityForCwd(metadata.cwd)) === targetRemote);
+        const cwdMatchesCurrentRepository = pathMatchesCurrentRepository || checkoutMatchesCurrentRepository;
+        const currentRepositoryRemote = cwdMatchesCurrentRepository ? targetRemote : null;
         const matchesCurrentRepository = options.repository
             ? remoteMatchesCurrentRepository ||
                 (!normalizedRemote && cwdMatchesCurrentRepository) ||

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@groundtrack/hooks",
-  "version": "0.1.15",
+  "version": "0.1.17",
   "description": "Lifecycle hook utilities for Groundtrack MCP clients.",
   "keywords": [
     "claude-code",

package/templates/AGENTS.md

@@ -1,4 +1,4 @@
-<!-- groundtrack:start version=4 -->
+<!-- groundtrack:start version=5 -->
 
 ## Groundtrack
 
@@ -8,7 +8,7 @@ Use Groundtrack as the shared engineering memory for this repository.
 - Before non-trivial investigation or implementation where prior decisions, failures, or constraints could matter, call `search_experiences`. Start with a focused description of the work, then inspect the results and search one or two materially different adjacent concepts when related components, constraints, failure modes, or prior decisions could change the approach. Do not stop merely because the first search has no exact match; try a meaningfully broader or neighboring query. Keep this expansion bounded, and also search before repeating an approach that may already have been tried.
 - When a relevant experience needs more context or verification, call `get_experience_events` with its id to inspect the underlying raw evidence and provenance.
 - Apply relevant current experiences and heed any caveats that an experience was contradicted, superseded, or expired.
-- Once the effect of a search is known, call `report_experience_use` with its retrieval id. Report when a result changed the approach or avoided a failure, and report `not_helpful` when none applied.
+- Only call `report_experience_use` if `search_experiences` returned experiences; skip it for empty results, even with a retrieval id. For non-empty results, report when one changed the approach or avoided a failure, and report `not_helpful` after review when none applied.
 - After a task reaches a concrete result, call `record_outcome` with a short title, a concise summary, and the retrieval ids for searches that contributed. Include measurements only for sourced, quantified impact on time, cost, reliability, quality, performance, or throughput; tests, typechecks, lint, and builds are validation rather than impact. Include avoided work only when it was explicitly estimated, and never infer unknown values.
 - After a non-obvious discovery, decision, workaround, correction, or failed approach that would help a future agent, call `store_event` promptly with a concise title and an explanation of what happened and why it matters.
 - Do not store routine implementation details, obvious facts, unrestricted transcripts, or secrets.