docs: update.

Author: knightedcodemonkey

docs/idb-workspace-state.md

@@ -46,6 +46,24 @@ If a value is required to accurately restore PR/workspace behavior after reload,
 
 `localStorage` should only mirror user preferences and lightweight bootstrap values.
 
+## Post-Push Baseline Invariant
+
+After a successful Push Commit action for an active PR workspace:
+
+- The active workspace record must persist immediately in IDB.
+- Any committed tab path returned by push updates must persist with:
+  - `isDirty = false`
+  - `syncedContent = content`
+  - `syncedAt` updated to the push/reconcile time
+  - `lastSyncedRemoteSha` set when a commit SHA is available
+- The same clean baseline must survive a full page reload.
+
+Dirty-state note:
+
+- When `syncedContent` is present for a tab, canonical dirty state is derived from
+  `content !== syncedContent`.
+- This prevents stale UI-only dirty flags from overriding persisted sync baseline truth.
+
 ## Behavioral Spec
 
 For action-level drawer semantics and state machine behavior, see:

docs/pr-context-storage-matrix.md

@@ -34,11 +34,12 @@ See the full storage ownership docs for non-PR keys:
 
 Use this matrix as the source of truth when debugging UI/storage mismatch.
 
-| Scenario                                  | IDB `prContextState` | IDB `prNumber`   | localStorage PR fields | Notes                                                |
-| ----------------------------------------- | -------------------- | ---------------- | ---------------------- | ---------------------------------------------------- |
-| A. Local workspace only, no PR context    | `inactive`           | `null`           | none                   | No connected PR context.                             |
-| B. Workspace is for an active, open PR    | `active`             | PR number        | none                   | Push mode in PR controls.                            |
-| C. Workspace is for a PR closed on GitHub | `closed`             | closed PR number | none                   | Historical context retained for debugging/reference. |
+| Scenario                                   | IDB `prContextState` | IDB `prNumber`   | localStorage PR fields | Notes                                                                                                           |
+| ------------------------------------------ | -------------------- | ---------------- | ---------------------- | --------------------------------------------------------------------------------------------------------------- |
+| A. Local workspace only, no PR context     | `inactive`           | `null`           | none                   | No connected PR context.                                                                                        |
+| B. Workspace is for an active, open PR     | `active`             | PR number        | none                   | Push mode in PR controls.                                                                                       |
+| C. Workspace is for a PR closed on GitHub  | `closed`             | closed PR number | none                   | Historical context retained for debugging/reference.                                                            |
+| D. Active PR immediately after push commit | `active`             | PR number        | none                   | Committed tabs persist clean baseline (`isDirty=false`, `syncedContent=content`) and remain clean after reload. |
 
 ## Current Workspace Selection On Load
 
@@ -80,6 +81,9 @@ When the UI does not match expected PR state:
    - `prContextState`
    - `prNumber`
    - `repo`, `head`, `prTitle`
+
+- committed tab fields: `isDirty`, `syncedContent`, `content`, `syncedAt`, `lastSyncedRemoteSha`
+
 2. Compare against the matrix above.
 3. If the PR is still open on GitHub, expect PR controls to return to Push mode and the workspace record to transition back to `active`.
 4. If the PR is no longer open, expect Open PR mode to remain and status messaging to explain verification results.