agents-handoff 0.0.0-stage → 2.0.2

package/docs/SESSIONS.md

@@ -0,0 +1,66 @@
+---
+title: Session index
+---
+
+# Session index
+
+A handoff store is a directory of captured sessions. This page is generated from the
+sample store in [`examples/sessions/`](https://github.com/Alot1z/agent-handoff/tree/main/examples/sessions), whose sessions the
+engine built from the two transcripts this repository ships. Nothing here is written by hand:
+the table below is a rendering of that store, re-checked on every build.
+
+| Project | Session | Harness | Turns | Revision | Manifest sha256 | Integrity |
+|---|---|---|---:|---:|---|---|
+| demo | `typescript-project-setup` | claude-code | 11 | 1 | `141e232eb2ad…` | PASS |
+| smoke-test | `fixture-roundtrip` | codex | 2 | 1 | `a81d076e3334…` | PASS |
+
+**2 session(s) across 2 project(s): all verified.**
+
+## What each column proves
+
+| Column | Where it comes from |
+|---|---|
+| Project, Session | The store layout: `projects/<project>/<session>/` |
+| Harness | `harness` in the session manifest — what produced the transcript |
+| Turns | Lines in `timeline.jsonl`, checked against `turn_count` in the manifest |
+| Revision | `revisions` in the manifest. A rebuild that appends turns raises it; it never forks a session |
+| Manifest sha256 | `manifest_sha256`, the hash of the manifest with that field removed |
+| Integrity | `PASS` when the manifest hash matches, the turn count matches and `HANDOFF.llm.json` parses |
+
+## Verify a session yourself
+
+Point the engine at the sample store and ask it the same question this page answers:
+
+```bash
+# the store this page is rendered from
+HANDOFFS_ROOT=examples/sessions node tools/handoff.mjs list
+HANDOFFS_ROOT=examples/sessions node tools/handoff.mjs verify typescript-project-setup
+HANDOFFS_ROOT=examples/sessions node tools/handoff.mjs verify fixture-roundtrip
+
+# your own store
+HANDOFFS_ROOT=/path/to/your/store node tools/handoff.mjs list
+```
+
+`verify` exits non-zero the moment one of the three checks fails, so it works as a gate:
+
+```bash
+HANDOFFS_ROOT=examples/sessions node tools/handoff.mjs verify typescript-project-setup || echo "do not resume this session"
+```
+
+## Generate this page from your own store
+
+The generator is part of this repository, and it reads any store in the format above:
+
+```bash
+node .github/scripts/build-sessions-index.mjs --store examples/sessions --out docs/SESSIONS.md
+node .github/scripts/build-sessions-index.mjs --check    # exit 1 when the page is stale
+```
+
+`--check` is wired into CI, so a store that changes without the page changing fails the build
+instead of publishing a table that no longer matches what the engine can read.
+
+## Next
+
+- The file-by-file contract for a session folder is in [FORMAT.md](FORMAT.md).
+- The commands that read and write a store are in [CLI.md](CLI.md).
+- What the hashes prove, and what they cannot, is in [PROVENANCE.md](PROVENANCE.md).

package/docs/TROUBLESHOOTING.md

@@ -0,0 +1,158 @@
+---
+title: Troubleshooting
+---
+
+# Troubleshooting
+
+Each entry names the symptom, the cause, and the fix. Exit codes are the ones documented in
+[CLI.md](CLI.md).
+
+## Nothing is listed
+
+**Symptom:** `handoff: no handoffs yet`.
+
+**Cause:** no build has run against the store being read, or the build wrote to a different
+store.
+
+**Fix:** check which store the engine resolved, and which rule chose it:
+
+```bash
+node tools/handoff.mjs config
+```
+
+The rule is one of `env`, `config`, `discover`, `default`. If it is not the store you
+expected, set `HANDOFFS_ROOT` for the run, or add a `handoff.config.json` at the project
+root. Resolution order is in [FORMAT.md](FORMAT.md#where-handoffs-live).
+
+## `build` exits 2
+
+**Cause:** `--source` was not given, or the value was consumed as another flag.
+
+**Fix:** `build` requires it:
+
+```bash
+node tools/handoff.mjs build --source transcript.jsonl --project my-project
+```
+
+## `build` exits 4 after reading the file
+
+**Cause:** no turn parsed. A `.jsonl` source is parsed one line at a time and a line that
+does not parse is skipped; a text source needs a line starting with `user:`, `human:`,
+`assistant:`, `ai:`, `system:` or `tool:`.
+
+**Fix:** inspect the first few lines of the source. If the transcript is JSONL but the fields
+are named differently, an adapter is what you want — see [ADAPTERS.md](https://github.com/Alot1z/agent-handoff/blob/main/refs/ADAPTERS.md)
+for the canonical shape, and [INTEGRATION.md](INTEGRATION.md) for mapping a new source onto
+it.
+
+## `verify` prints FAIL
+
+**Cause:** one of three things — the manifest was edited by hand after the build, the
+timeline line count no longer matches `turn_count`, or `HANDOFF.llm.json` does not parse.
+
+**Fix:** do not edit a handoff by hand. Rebuild from the same source:
+
+```bash
+node tools/handoff.mjs build --source <original source> --session <id>
+```
+
+A rebuild re-seals the manifest and rewrites the renders. If the original source is gone,
+the handoff cannot be re-verified, and the honest answer is to say so rather than patch the
+hash.
+
+## `show`, `verify`, `rename` or `retitle` exits 3 or 4
+
+**Cause:** 3 means the prefix matched more than one session; 4 means it matched none.
+
+**Fix:** run `handoff.mjs list`, then use a longer prefix.
+
+## `config` exits 2 and names a config file
+
+**Cause:** a `handoff.config.json` was found but is not valid against
+`handoff.config.schema.json`. The engine refuses to fall back to another store, because
+falling back would write somewhere other than the configured location.
+
+**Fix:** correct the file against the schema, or delete it to fall through to the
+`handoffs/` convention.
+
+## A runtime command exits 3 with "capture already in flight"
+
+**Cause:** another run holds the lock for that project and session. Locks are files in
+`<root>/.locks/`, named after a hash of the operation target.
+
+**Fix:** wait for the other run. If a previous process was killed abruptly, it can leave a
+lock file behind; the file is normally removed when the run finishes, so a lock that is
+still present after every process has stopped can be deleted by hand.
+
+## `dispatch` or `merge` produced something that fails the gate
+
+**Cause:** by design. A `merge` writes a timeline with no brief, no payload and no
+`TOOLS.md`, so `verify-gate` fails it on `payload` and `contract` until a brief is written
+for the merged session. `index` reports the same sessions as stale.
+
+**Fix:** write the brief for the merged session, then re-run `verify-gate`. A brief needs the
+seven contract fields — `RESULT`, `WHAT_CHANGED`, `VALIDATION`, `EVIDENCE`, `BLOCKERS`,
+`RISKS`, `FOLLOW_UP` — each starting a line.
+
+## `verify-gate` exits 0 but the verdict says REJECTED
+
+**Cause:** not a bug. `verify-gate` exits 0 for both verdicts so that "the gate ran" and
+"the gate passed" stay distinguishable. Read `ok` or `verdict` from the JSON.
+
+**Fix:** branch on the verdict in any script that calls it. The same applies to `promote`,
+which prints the gate result but stamps the manifest either way.
+
+## `promote` stamped a session that is not verified
+
+**Cause:** expected behaviour, and stated in the command reference. Promotion is a local
+stamp, not an enforcement.
+
+**Fix:** run `verify-gate` first and only call `promote` when the verdict is `VERIFIED`.
+
+## `capability-registry check` fails with `unknown`
+
+**Cause:** a capability declares a probe kind with no implementation, or declares no target
+or command for its kind. The registry reports `unknown` with the reason instead of guessing.
+
+**Fix:** read the evidence line for the capability. `unknown` for a required capability is
+treated as a failure on purpose: an unanswered question is not a pass.
+
+## `runtime-engine run` exits 3
+
+**Cause:** `DENIED`. An explicit denial, a personal-data path, an unknown risk class or an
+unknown grant all land here. A personal-data or denied target is refused at any risk class.
+
+**Fix:** inspect the decision before changing anything:
+
+```bash
+node tools/runtime-engine.mjs evaluate --risk R1 --target <path> --json
+```
+
+The policy itself is [permission-policy.json](https://github.com/Alot1z/agent-handoff/blob/main/permission-policy.json); read
+[PERMISSIONS.md](PERMISSIONS.md) for the levels.
+
+## `runtime-engine resume` exits 4
+
+**Cause:** there is no checkpoint to resume from, either because no job ran for that session
+or because the session name does not match. Exit 5 means a checkpoint exists but is corrupt
+or its integrity seal does not match.
+
+**Fix:** run `status` for the session to see the durable state, then start a new job.
+
+## The documentation site is missing a page, or a link 404s
+
+**Cause:** the site is built from `docs/`. A page not listed in `docs/_data/nav.yml` does not
+appear in the navigation, and a relative link that points at a file outside `docs/` does not
+resolve in the built site.
+
+**Fix:** add the page under `docs/`, add it to `nav.yml`, and run the check CI runs:
+
+```bash
+node .github/scripts/check-docs.mjs
+```
+
+## Node version
+
+The tools require Node.js 18 or newer and use only built-in modules. `node --version` below
+18 is the only unsupported configuration; there is no build step and no dependencies to
+reinstall. Platform notes are in [COMPATIBILITY.md](COMPATIBILITY.md).

package/docs/UNINSTALL.md

@@ -0,0 +1,122 @@
+---
+title: Uninstall
+---
+
+# Uninstall
+
+Uninstalling removes the skill files. Your handoffs and your configuration stay where they are.
+
+## Quick uninstall
+
+```bash
+npx agents-handoff --remove
+```
+
+Removal asks for confirmation first:
+
+```
+This will remove agent-handoff from:
+  <install-path>
+
+Your handoffs (projects/, handoffs/, links/) will NOT be deleted.
+Configuration (handoff.config.json) will NOT be deleted.
+
+Continue? (y/N)
+```
+
+Answer `y` to proceed. In a non-interactive shell the prompt is skipped and nothing is removed;
+the installer prints `Non-interactive mode, use --force to skip confirmation` instead.
+
+```bash
+npx agents-handoff --remove --force
+```
+
+## Options
+
+| Option | Effect |
+|---|---|
+| `--remove` | Remove the installation (interactive confirmation). |
+| `--force`, `-f` | Skip the confirmation, and delete the kept directories when they are empty. |
+| `--location <global\|local\|project>` | Which installation to remove. Global is the default and is resolved the same way as for install. |
+| `--path <dir>` | Remove the installation at exactly this directory. |
+
+Flag form and bare verb are equivalent: `--remove` and `remove`, `--force` and `-f`.
+
+## What is removed
+
+Everything in the installation directory, except the entries listed in the next section:
+
+- the engine and runtime: `tools/`, `tools/lib/`
+- metadata: `SKILL.md`, `skill.json`, `package.json`, the manifest JSON files
+- `schemas/`, `refs/`, `templates/`, `docs/`, `tests/`
+- `INDEX.json` and any other generated file in that directory
+
+Each removed entry is printed as `Removed file: <name>` or `Removed directory: <name>/`.
+
+## What is kept
+
+| Kept | Why |
+|---|---|
+| `handoffs/`, `projects/`, `links/` | Your session data. |
+| `handoff.config.json` | Your configuration. |
+| `.env.example` | Your environment template. |
+| Anything you added elsewhere in the directory | The installer only removes entries it walks past; it never deletes a directory it keeps. |
+
+With `--force`, the three data directories are still kept unless they are empty, in which case
+they are removed and reported as `Removed empty directory: <name>/`. After that, if the
+installation directory itself is empty it is removed too. If handoffs remain in it, the
+directory stays.
+
+## Manual uninstall
+
+Remove the skill files and leave the data behind:
+
+```bash
+cd "<install-path>"
+
+# Keep these: handoffs/ projects/ links/ handoff.config.json .env.example
+rm -rf tools docs refs templates schemas src tests
+rm -f SKILL.md skill.json package.json INDEX.json \
+      capability-registry.json permission-policy.json \
+      handoff.config.schema.json handoff.config.example.json
+```
+
+If you never store handoffs inside the installation — for example when `HANDOFFS_ROOT` points
+somewhere else — and you do not need anything else in it, the whole directory can go:
+
+```bash
+rm -rf "<install-path>"
+```
+
+Check where handoff data actually lives before doing that:
+
+```bash
+node "<install-path>/tools/handoff.mjs" config
+```
+
+`handoff: config root=<dir>` is the directory that holds your handoffs.
+
+## After uninstalling
+
+```bash
+npx agents-handoff --list
+```
+
+The removed location should no longer appear. Handoff data that was kept still exists on disk
+and can be read by a later installation, or by any tool that reads a handoff folder directly.
+
+## Troubleshooting
+
+| Symptom | Cause and fix |
+|---|---|
+| `Not installed at <dir>` | That location holds no installation. Check `--list` and `where`, then retry with the right `--location` or `--path`. |
+| Nothing was removed | The confirmation was skipped. Pass `--force`. |
+| `EPERM` or `EBUSY` on Windows | A process is holding the files. Close it and retry, or check file attributes. |
+| Permission denied | The installation is outside your user directory. Remove it with the privileges that created it, or use `--force` from a shell that can write there. |
+| Handoff data disappeared | It was an empty kept directory removed by `--force`, or `HANDOFFS_ROOT` points elsewhere. Check the root printed by `handoff.mjs config`. |
+
+## See also
+
+- [INSTALL.md](INSTALL.md)
+- [UPGRADE.md](UPGRADE.md)
+- [../README.md](https://github.com/Alot1z/agent-handoff/blob/main/README.md)

package/docs/UPGRADE.md

@@ -0,0 +1,139 @@
+---
+title: Upgrade
+---
+
+# Upgrade
+
+An upgrade replaces skill files. It does not touch the handoff folders, the configuration, or
+anything you added next to them.
+
+## Before upgrading
+
+Confirm what is installed:
+
+```bash
+npx agents-handoff --list
+```
+
+`--list` prints each installed location with its version and the number of manifest files
+present. The version also appears as `version:` in the `SKILL.md` front matter of the
+installation.
+
+Back up handoff data before any manual change. The upgrade path keeps it, but a copy costs
+nothing:
+
+```bash
+cp -r handoffs/ handoffs-backup/
+```
+
+Note any local edits to `handoff.config.json`, since a reinstall overwrites skill files but
+leaves that file alone.
+
+## Upgrade with the installer
+
+```bash
+npx agents-handoff --update
+```
+
+`--update` requires an existing installation; without one it exits with
+`Not installed at <dir>. Run 'install' first.`
+
+The update then reinstalls: the skill files are copied over the existing installation and
+overwrite the files of the same name. Files that are not part of the installation manifest —
+`handoffs/`, `projects/`, `links/`, `handoff.config.json`, `.env.example`, and anything you added
+— are left in place.
+
+To update into a specific location or version:
+
+```bash
+npx agents-handoff --update --location project
+npx agents-handoff --update --version 2.0.0
+```
+
+`--version` installs the version you ask for: the tree beside the installer when there is one
+(a checkout, a release archive), or the archive of that version's tag when there is not (the
+published package carries the installer alone). Confirm what is actually installed with
+`--verify`, which prints the version read back from the installed `SKILL.md`, rather than
+trusting the request.
+
+## Manual upgrade
+
+Replace the skill files and keep the data:
+
+1. Extract the release archive (`agent-handoff-latest.zip`, or
+   `agent-handoff-v<version>.zip`) to a temporary directory.
+2. Copy the skill files over the installation: `SKILL.md`, `skill.json`, the manifest JSON
+   files, `tools/`, `tools/lib/`, `schemas/`, `refs/`, `templates/`, `docs/`, `tests/`.
+3. Do not delete `handoffs/`, `projects/`, `links/`, or `handoff.config.json`.
+
+```bash
+unzip agent-handoff-latest.zip -d /tmp/agent-handoff-new
+cp -r /tmp/agent-handoff-new/tools/ /tmp/agent-handoff-new/refs/ \
+      /tmp/agent-handoff-new/templates/ /tmp/agent-handoff-new/schemas/ \
+      /tmp/agent-handoff-new/docs/ "<install-path>/"
+cp /tmp/agent-handoff-new/SKILL.md /tmp/agent-handoff-new/skill.json "<install-path>/"
+```
+
+## What an upgrade changes
+
+| Changed | Unchanged |
+|---|---|
+| `tools/` — the engine and the dynamic runtime | `handoffs/` — your session data |
+| `refs/`, `templates/`, `schemas/`, `docs/` | `projects/`, `links/` |
+| `SKILL.md`, `skill.json`, manifest JSON files | `handoff.config.json` and your edits |
+| `install/` — the installer itself | `HANDOFFS_ROOT`, if you use it |
+
+Handoff folders are read from the handoff root in place, so an upgrade does not move or rewrite
+them.
+
+## After upgrading
+
+```bash
+npx agents-handoff --verify
+node "<install-path>/tools/handoff.mjs" config
+node "<install-path>/tools/handoff.mjs" list
+```
+
+`config` proves the engine starts and prints the handoff root it resolved. `list` proves the
+engine still finds the handoff folders that were already there.
+
+The shipped test suite is a stronger check and does not touch existing handoffs when you point
+it at a scratch root:
+
+```bash
+HANDOFFS_ROOT=/tmp/handoff-check node "<install-path>/tools/handoff.test.mjs"
+```
+
+Read an existing handoff to confirm the data survived:
+
+```bash
+node "<install-path>/tools/handoff.mjs" show <id-prefix>
+node "<install-path>/tools/handoff.mjs" verify <id-prefix>
+```
+
+`verify <id-prefix>` recomputes the stored handoff's manifest hash, so it fails loudly if an
+upgrade damaged the folder.
+
+## Rollback
+
+1. Restore the previous version's skill files: extract that version's release archive and copy
+   the skill files over the installation, as in the manual upgrade above.
+2. Or reinstall the files that ship with the installer: `npx agents-handoff --force`.
+3. Restore handoffs from your backup if you made one, and confirm with `--verify` and
+   `handoff.mjs list`.
+
+## Troubleshooting
+
+| Symptom | Cause and fix |
+|---|---|
+| `Not installed at <dir>` | Nothing to update at that location. Check `--list`, or drop `--location`/`--path`. |
+| Reported version did not change | The installer installs the tree beside it when there is one, so running it from a checkout installs that checkout. Use the published package, or pass `--version <x>` to fetch a tagged archive. |
+| Verification fails after an upgrade | A file is missing or the engine cannot start. Reinstall with `--force` and read the failing check. |
+| Handoffs no longer listed | The engine is reading a different root. Run `config` and compare it with where your handoffs live; set `HANDOFFS_ROOT` if needed. |
+| Configuration was overwritten | `handoff.config.json` is preserved, but a manual copy step can still overwrite it. Restore your backup. |
+
+## See also
+
+- [INSTALL.md](INSTALL.md)
+- [UNINSTALL.md](UNINSTALL.md)
+- [../README.md](https://github.com/Alot1z/agent-handoff/blob/main/README.md)

package/docs/_config.yml

@@ -0,0 +1,16 @@
+title: agent-handoff
+description: Cross-harness capture and verified continuation for AI working sessions.
+url: https://alot1z.github.io
+baseurl: /agent-handoff
+plugins:
+  - jekyll-relative-links
+relative_links:
+  enabled: true
+  collections: false
+defaults:
+  - scope:
+      path: ""
+    values:
+      layout: default
+exclude:
+  - README.md

package/docs/_data/nav.yml

@@ -0,0 +1,36 @@
+- title: Overview
+  path: /index.html
+- title: Install
+  path: /INSTALL.html
+- title: Upgrade
+  path: /UPGRADE.html
+- title: Uninstall
+  path: /UNINSTALL.html
+- title: Architecture
+  path: /ARCHITECTURE.html
+- title: Command reference
+  path: /CLI.html
+- title: Handoff format
+  path: /FORMAT.html
+- title: Session index
+  path: /SESSIONS.html
+- title: Integration
+  path: /INTEGRATION.html
+- title: Runtime layer
+  path: /LEVEL4.html
+- title: Dispatch
+  path: /LEVEL5.html
+- title: Permissions
+  path: /PERMISSIONS.html
+- title: Security
+  path: /SECURITY.html
+- title: Compatibility
+  path: /COMPATIBILITY.html
+- title: Provenance
+  path: /PROVENANCE.html
+- title: Troubleshooting
+  path: /TROUBLESHOOTING.html
+- title: Changelog
+  path: /CHANGELOG.html
+- title: Contributing
+  path: /CONTRIBUTING.html

package/docs/_layouts/default.html

@@ -0,0 +1,31 @@
+<!DOCTYPE html>
+<html lang="en">
+<head>
+<meta charset="utf-8">
+<meta name="viewport" content="width=device-width, initial-scale=1">
+<title>{% if page.title and page.title != site.title %}{{ page.title }} · {{ site.title }}{% else %}{{ site.title }}{% endif %}</title>
+<meta name="description" content="{{ page.description | default: site.description }}">
+<link rel="stylesheet" href="{{ '/assets/style.css' | relative_url }}">
+</head>
+<body>
+<header class="top">
+  <a class="brand" href="{{ '/' | relative_url }}">{{ site.title }}</a>
+  <span class="tag">{{ site.description }}</span>
+</header>
+<div class="wrap">
+  <nav class="side">
+    <p class="navhead">Documentation</p>
+    <ul>
+      {% for d in site.data.nav %}<li><a href="{{ d.path | relative_url }}">{{ d.title }}</a></li>
+      {% endfor %}
+    </ul>
+  </nav>
+  <main>
+{{ content }}
+  </main>
+</div>
+<footer class="foot">
+  MIT licensed · <a href="{{ site.baseurl }}">repository</a> · documentation source: the docs/ directory of this project
+</footer>
+</body>
+</html>

package/docs/assets/style.css

@@ -0,0 +1,88 @@
+:root {
+  --bg: #ffffff;
+  --fg: #1f2328;
+  --muted: #59636e;
+  --line: #d1d9e0;
+  --link: #0969da;
+  --code: #f6f8fa;
+}
+@media (prefers-color-scheme: dark) {
+  :root {
+    --bg: #0d1117;
+    --fg: #e6edf3;
+    --muted: #9198a1;
+    --line: #30363d;
+    --link: #4493f8;
+    --code: #161b22;
+  }
+}
+* { box-sizing: border-box; }
+body {
+  margin: 0;
+  background: var(--bg);
+  color: var(--fg);
+  font: 16px/1.6 -apple-system, BlinkMacSystemFont, "Segoe UI", Helvetica, Arial, sans-serif;
+}
+a { color: var(--link); text-decoration: none; }
+a:hover { text-decoration: underline; }
+.top {
+  display: flex;
+  flex-wrap: wrap;
+  align-items: baseline;
+  gap: 0.75rem;
+  padding: 1rem 1.5rem;
+  border-bottom: 1px solid var(--line);
+}
+.brand { font-weight: 600; font-size: 1.05rem; color: var(--fg); }
+.tag { color: var(--muted); font-size: 0.85rem; }
+.wrap {
+  display: flex;
+  align-items: flex-start;
+  gap: 2.5rem;
+  max-width: 1080px;
+  margin: 0 auto;
+  padding: 2rem 1.5rem 4rem;
+}
+.side { flex: 0 0 180px; position: sticky; top: 1rem; }
+.navhead {
+  margin: 0 0 0.5rem;
+  font-size: 0.75rem;
+  letter-spacing: 0.06em;
+  text-transform: uppercase;
+  color: var(--muted);
+}
+.side ul { list-style: none; margin: 0; padding: 0; }
+.side li { margin: 0.15rem 0; }
+.side a { font-size: 0.9rem; }
+main { flex: 1 1 auto; min-width: 0; }
+main h1 { font-size: 1.75rem; margin: 0 0 1rem; }
+main h2 { font-size: 1.2rem; margin: 2rem 0 0.6rem; padding-bottom: 0.25rem; border-bottom: 1px solid var(--line); }
+main h3 { font-size: 1rem; margin: 1.5rem 0 0.4rem; }
+code {
+  background: var(--code);
+  padding: 0.1em 0.35em;
+  border-radius: 5px;
+  font-size: 0.88em;
+  font-family: ui-monospace, SFMono-Regular, "SF Mono", Menlo, Consolas, monospace;
+}
+pre {
+  background: var(--code);
+  padding: 0.85rem 1rem;
+  border-radius: 6px;
+  overflow-x: auto;
+}
+pre code { background: none; padding: 0; }
+table { border-collapse: collapse; width: 100%; margin: 1rem 0; font-size: 0.92rem; }
+th, td { border: 1px solid var(--line); padding: 0.4rem 0.6rem; text-align: left; vertical-align: top; }
+th { background: var(--code); }
+blockquote { margin: 1rem 0; padding: 0 1rem; border-left: 3px solid var(--line); color: var(--muted); }
+.foot {
+  border-top: 1px solid var(--line);
+  padding: 1rem 1.5rem 2rem;
+  color: var(--muted);
+  font-size: 0.85rem;
+}
+@media (max-width: 720px) {
+  .wrap { flex-direction: column; gap: 1rem; }
+  .side { position: static; }
+}