opencode-forgekeeper 2.0.0 → 2.1.1

package/README.md

@@ -148,6 +148,11 @@ reuses a branch's PR/MR number for up to 10 minutes.
 Explicit targets that aren't PRs/MRs, such as issues, show no status. Unresolved explicit
 PRs/MRs never fall back to the branch.
 
+Without a PR/MR to show, the footer stays empty, even when a lookup fails, such as in a new
+session before the server answers. It shows `PR/MR status unavailable` only when none of
+the session's explicit PR/MR targets can be looked up or found. `/forge-status` explains
+why.
+
 The server runs at most four `glab` or `gh` commands at once for status and review
 feedback, across all sessions. When some target lookups fail, the footer shows the others
 and counts the failures as `N unavailable`. A target whose lookup failed with an error
@@ -332,9 +337,11 @@ OpenCode scopes plugin storage by plugin ID, so nothing stored under the former
 `opencode-forge-session-title`, carries over:
 
 - Sessions start in branch-based naming. Ask the agent to set their targets again.
-- A title that kept a single-reference prefix from before, such as `[!456] Review`, can get a
-  second prefix, such as `[#12, !45] [!456] Review`. Remove the older one by hand. Older prefixes
-  with two references, such as `[#12, !45]`, are replaced automatically.
+- A title that kept a single-reference prefix from before, such as `[!456] Review`, now looks
+  like a reference that you wrote. Until you set a target, the status follows that PR/MR, labeled
+  "from the session title". Setting a target adds a second prefix, such as
+  `[#12, !45] [!456] Review`. Remove the older prefix by hand. Older prefixes with two
+  references, such as `[#12, !45]`, are replaced automatically.
 - The first look at each PR/MR records a new review baseline, so comments posted before then
   aren't announced.
 - Callers of the RPC need the new ID, `opencode-forgekeeper`.