uniweb 1.21.0 → 1.21.2

package/src/framework-index.json

@@ -1,12 +1,12 @@
 {
   "schemaVersion": 1,
-  "generatedAt": "2026-10-26T02:00:48.151Z",
+  "generatedAt": "2026-10-26T17:53:53.949Z",
   "packages": {
     "@uniweb/api": {
       "version": "1.6.4"
     },
     "@uniweb/build": {
-      "version": "1.10.2"
+      "version": "1.10.4"
     },
     "@uniweb/content-reader": {
       "version": "1.5.7"

package/src/index.js

@@ -1777,17 +1777,25 @@ ${colors.cyan}${colors.bright}uniweb status${colors.reset} ${colors.dim}— What
 ${colors.bright}Usage:${colors.reset}
   uniweb status [options]
 
-Run it when you begin, before you push, and after a command refuses. It checks:
+Run it when you begin, when you come back to the project, before you push, publish
+or deploy, and after a command refuses. It opens with what the site is — synced
+where, live where, deployed where — and checks:
 
+  project  the workspace's sites and foundations, the foundation this site is built
+           with and the other sites it reaches, pages from outside the site's folder,
+           the languages
   git      conflicts, a merge waiting, the site's files not committed, the git remote
-  app      the session, what changed on the backend since this copy last synced,
-           what is not pushed, whether the site is live, who has it open in the app,
-           the foundation
+  app      the session, what changed on the backend since this copy last synced —
+           the files a pull would change — what is not pushed, who has the site
+           open in the app, the foundation
+  hosting  where the site is live, the other hosts deploy.yml lists (by CI or by
+           hand, and how far behind), and the services the live site has
   uniweb   whether a newer release is out
   health   doctor's findings
   dev      the dev server
 
-and ends with the steps to take, in the order to take them. A step marked
+and ends with the steps to take, in the order to take them. At the root of a
+workspace with several sites, it says what each one is. A step marked
 "ask the person first" is theirs to decide — going live, for one.
 
 It changes nothing and asks nothing: with no session it says how to sign in.

package/src/utils/status-next.js

@@ -7,13 +7,13 @@
  * then sends the reader back up. So the order is one table, not each check's own idea:
  *
  *   sign in → settle conflicts → finish a merge → take what others did (refresh, or pull)
- *   → push → push to git → go live → update Uniweb → read doctor's findings
+ *   → push → push to git → go live → deploy to another host → update Uniweb → read doctor's findings
  *
  * Each check proposes steps by name (`step`); this sorts them, folds the ones another step
  * already does, and drops duplicates.
  */
 
-const ORDER = ['login', 'conflicts', 'merge', 'refresh', 'pull', 'push', 'gitpush', 'publish', 'update', 'doctor']
+const ORDER = ['login', 'conflicts', 'merge', 'refresh', 'pull', 'push', 'gitpush', 'publish', 'deploy', 'update', 'doctor']
 
 /**
  * @param {Array<{ step: string, command: string|null, why: string, ask?: boolean }>} proposals

package/src/utils/sync-point.js

@@ -382,7 +382,7 @@ function differsIn(repo, a, b, roots) {
  * @param {string[]} opts.roots - the site's content roots, relative to the site
  * @param {string|null} opts.rev - the commit whose content the roots are filled from;
  *   null for none
- * @returns {{ siteDir: string, commit: Function, placeIgnored: Function, close: Function }}
+ * @returns {{ siteDir: string, commit: Function, changes: Function, placeIgnored: Function, close: Function }}
  */
 export function openStandIn(repo, { roots, rev }) {
   for (const r of roots) {
@@ -543,6 +543,24 @@ export function openStandIn(repo, { roots, rev }) {
       return placed
     }
 
+    /**
+     * What is written under the roots that `rev` does not hold so — each `[status, path]`,
+     * status `A`, `M` or `D`, the path relative to the site. Asked of the stand-in's own
+     * index, which holds `rev`: nothing is staged, committed or written to the repository.
+     * What the repository ignores is no change, as for `commit`.
+     * @returns {Array<[string, string]>}
+     */
+    const changes = () => {
+      const roots = full.filter((f) => present.includes(f) || existsSync(join(root, f)))
+      if (!roots.length) return []
+      const site = (p) => (sitePrefix && p.startsWith(sitePrefix) ? p.slice(sitePrefix.length) : p)
+      const out = []
+      const tracked = zlist(at(['diff', '--name-status', '-z', '--no-renames', '--', ...roots]))
+      for (let i = 0; i + 1 < tracked.length; i += 2) out.push([tracked[i], site(tracked[i + 1])])
+      for (const p of zlist(at(['ls-files', '--others', '--exclude-standard', '-z', '--', ...roots]))) out.push(['A', site(p)])
+      return out.sort((a, b) => (a[1] < b[1] ? -1 : a[1] > b[1] ? 1 : 0))
+    }
+
     // The roots git can hold here. ⛔ One the repository ignores whole is not named to
     // `git add`, which refuses an ignored path; what is written under it is placed instead.
     const held = (paths) => {
@@ -556,7 +574,7 @@ export function openStandIn(repo, { roots, rev }) {
       return paths.filter((p) => !ignored.includes(p))
     }
 
-    return { siteDir, commit, placeIgnored, close }
+    return { siteDir, commit, changes, placeIgnored, close }
   } catch (err) {
     close()
     throw err