@@ -80,10 +80,12 @@ database does not have.
   writes code, and it says the value objects were emitted only when `entityFile()` (or another
   entity-module generator) ran. Found by an adopter on 1.1.0-rc.4.
 - **`agentDocsFile()` says when it skips `agent/ui.md`.** The page is written only when the run
-  lists a client UI generator or the generator is given `includeUiTier: true`, and before this
-  a project whose UI is generated by a separate config lost the page with no message. `meta
-  gen` now warns `agent/ui.md not written: no client UI generator in this run; set
-  includeUiTier: true if another config generates the UI.`, and the option is documented in
+  lists a client UI generator or the config sets `includeUiTier: true`, and before this a
+  project whose UI is generated by a separate config lost the page with no message. When the
+  config leaves `includeUiTier` unset, `meta gen` now warns `agent/ui.md not written: no client
+  UI generator in this run; set includeUiTier: true if another config generates the UI, or
+  includeUiTier: false if there is no UI.` A project with no UI anywhere sets `includeUiTier:
+  false`, which skips the page without the warning. Both settings are documented in
   `docs/features/migrations/docs-are-generators.md`. Found by an adopter on 1.1.0-rc.4.
 - **A pre-release CLI's version in `.metaobjects/.agent-context.json` is caught.** `meta init`
   stamps the running CLI's version into that committed file's `generatedBy`; run with a release
@@ -100,7 +102,9 @@ database does not have.
 - **`prerelease-link unlink` removes the git exclude lines `link` added.** `link` appended its
   ignore rules as bare lines to the clone's shared `info/exclude`, and `unlink` left them there.
   They now sit in one managed block, which `unlink` removes without touching a line the user
-  wrote, and a repeated `link` does not add them twice.
+  wrote, and a repeated `link` does not add them twice. The file is shared by every worktree
+  of the clone, so an entry another linked worktree still needs stays until that worktree is
+  unlinked.
 - `verify --codegen` (Python, C#) says when the committed output was generated with another
   column rule, another table rule, or both, and names the `naming` setting that reproduces it,
   instead of advising a regeneration that would commit the wrong column or table names.
 
@@ -21,7 +21,7 @@ generate, docs included). Each factory is an ordinary entry in `generators`, fro
 | `docsFile()` | `docs` | the neutral model surface — one page per entity and per template (`<Entity>.md`, `<Template>.md`), plus an overview with the whole-model ER diagram. Options: `apiSurfaces`, `templates`. |
 | `apiDocsFile()` | `api-docs` | the api reference — `api/<Entity>.md`, `api/README.md`, `api/AGENT-API.md`: the concrete imports, signatures, payload field shapes and runnable examples for THIS project's generated code. Options: `subDir` (default `api`), `modelBaseUrl`. |
 | `requirementsFile()` | `requirements` | the declared `requirement.*` ledger, each entry headed by its dotted path and `title`. Writes nothing for a model with no `requirement.*` node. |
-| `agentDocsFile()` | `agent-docs` | `agent/schema.md`, `agent/ui.md` (only when the run also lists a client-tier generator, OR the config sets `includeUiTier: true` — the escape hatch for a docs-only config whose UI is generated by a separate config; skipping it with a UI surface in the model prints an advisory naming `includeUiTier`) and `agent/requirements.md` — the three `agent/` pages the always-on pointer reads before touching a tier. |
+| `agentDocsFile()` | `agent-docs` | `agent/schema.md`, `agent/ui.md` (only when the run also lists a client-tier generator, OR the config sets `includeUiTier: true` — the escape hatch for a docs-only config whose UI is generated by a separate config; skipping it with a UI surface in the model and `includeUiTier` unset prints an advisory naming `includeUiTier`; `includeUiTier: false` says there is no UI anywhere and skips it without one) and `agent/requirements.md` — the three `agent/` pages the always-on pointer reads before touching a tier. |
 | `metamodelDocsFile()` | `metamodel-docs` | the built-in vocabulary reference, under `metamodel/` (was `meta docs --metamodel`). |
 | `docsSiteFile()` | `docs-site` | an HTML site under `site/` (was `meta docs --site`). Option: `prompts`. `meta eject docs-site` copies its templates and assets to `codegen/docs-site/` (was `meta docs --scaffold-site`). |
 
 
@@ -145,7 +145,7 @@ them only if you ran those flags.
 |---|---|
 | `docs.outDir`, `--out` (default `./docs/generated`) | `targets.docs.outDir` |
 | `docs.layout`, `--layout` | `targets.docs.outputLayout` (falls back to the top-level `outputLayout`, as 1.0 did) |
-| `docs.surfaces`, `--model` / `--api` / `--requirements` / `--agent` | which factories you list: `docsFile()`, `apiDocsFile()`, `requirementsFile()`, `agentDocsFile()`. `--agent` wrote all three agent pages unconditionally; `agentDocsFile()` writes `agent/ui.md` only when the run also lists a client UI generator (a form, a hook, a grid or its columns) or the config sets `includeUiTier: true` — see "Things that are different in 1.1.0" |
+| `docs.surfaces`, `--model` / `--api` / `--requirements` / `--agent` | which factories you list: `docsFile()`, `apiDocsFile()`, `requirementsFile()`, `agentDocsFile()`. `--agent` wrote all three agent pages unconditionally; `agentDocsFile()` writes `agent/ui.md` only when the run also lists a client UI generator (a form, a hook, a grid or its columns) or the config sets `includeUiTier: true`; with `includeUiTier` unset it warns when it skips the page, and `includeUiTier: false` (no UI anywhere) skips it quietly — see "Things that are different in 1.1.0" |
 | `docs.apiSurfaces` | `docsFile({ apiSurfaces })`, same shape. Leave it out when the only api pages are this project's own: the model pages then link to whatever `apiDocsFile()` writes to the same target |
 | the `subDir` of the `ts` entry in `docs.apiSurfaces` (default `api`) | `apiDocsFile({ subDir })`, same default |
 | `docs.baseUrl`, `--base-url` | none: 1.0 read it nowhere. To link each api page to model pages hosted elsewhere, use `apiDocsFile({ modelBaseUrl })` |
@@ -178,8 +178,10 @@ them only if you ran those flags.
   whether a UI is emitted is a generator fact, not a metadata one. A **docs-only** config
   — one whose own `generators` lists no UI generator because a separate config generates
   the UI — never sees that generator, so set `includeUiTier: true` to write the page
-  anyway. When the model has a UI surface but the page is skipped, `meta gen` prints an
-  advisory naming `includeUiTier: true` rather than exiting silently.
+  anyway. When the model has a UI surface, the page is skipped and the config leaves
+  `includeUiTier` unset, `meta gen` prints an advisory naming `includeUiTier: true` rather
+  than exiting silently. A project with no UI anywhere (a server-only backend) sets
+  `includeUiTier: false`, which skips the page without the advisory.
 
 **Scripts and CI.** Replace `meta docs` with `meta gen`, and `meta verify --docs` with
 `meta verify --codegen`. To write only the documentation, name the docs entries:
 
@@ -171,7 +171,9 @@ the project's `.git/info/exclude`, which is local and not committed — in a lin
 worktree this is the *shared* exclude file in the clone's common dir (git has no
 per-worktree exclude), so the paths `link` adds there live inside their own managed block
 too: `unlink` removes exactly that block, never a line a user added to the file by hand,
-and a repeated `link` does not duplicate it. Files that *are* tracked by definition
+and a repeated `link` does not duplicate it. An entry that another worktree of the same
+clone still needs, because its own managed file is still linked, stays until that worktree
+is unlinked too. Files that *are* tracked by definition
 (`pyproject.toml`, `pom.xml`) get a loud warning instead — there is no way to make an edit
 to a tracked file uncommittable, which is precisely why the detector in §5 exists.
 
 
@@ -21,7 +21,7 @@ generate, docs included). Each factory is an ordinary entry in `generators`, fro
 | `docsFile()` | `docs` | the neutral model surface — one page per entity and per template (`<Entity>.md`, `<Template>.md`), plus an overview with the whole-model ER diagram. Options: `apiSurfaces`, `templates`. |
 | `apiDocsFile()` | `api-docs` | the api reference — `api/<Entity>.md`, `api/README.md`, `api/AGENT-API.md`: the concrete imports, signatures, payload field shapes and runnable examples for THIS project's generated code. Options: `subDir` (default `api`), `modelBaseUrl`. |
 | `requirementsFile()` | `requirements` | the declared `requirement.*` ledger, each entry headed by its dotted path and `title`. Writes nothing for a model with no `requirement.*` node. |
-| `agentDocsFile()` | `agent-docs` | `agent/schema.md`, `agent/ui.md` (only when the run also lists a client-tier generator, OR the config sets `includeUiTier: true` — the escape hatch for a docs-only config whose UI is generated by a separate config; skipping it with a UI surface in the model prints an advisory naming `includeUiTier`) and `agent/requirements.md` — the three `agent/` pages the always-on pointer reads before touching a tier. |
+| `agentDocsFile()` | `agent-docs` | `agent/schema.md`, `agent/ui.md` (only when the run also lists a client-tier generator, OR the config sets `includeUiTier: true` — the escape hatch for a docs-only config whose UI is generated by a separate config; skipping it with a UI surface in the model and `includeUiTier` unset prints an advisory naming `includeUiTier`; `includeUiTier: false` says there is no UI anywhere and skips it without one) and `agent/requirements.md` — the three `agent/` pages the always-on pointer reads before touching a tier. |
 | `metamodelDocsFile()` | `metamodel-docs` | the built-in vocabulary reference, under `metamodel/` (was `meta docs --metamodel`). |
 | `docsSiteFile()` | `docs-site` | an HTML site under `site/` (was `meta docs --site`). Option: `prompts`. `meta eject docs-site` copies its templates and assets to `codegen/docs-site/` (was `meta docs --scaffold-site`). |
 
 
@@ -21,7 +21,7 @@ generate, docs included). Each factory is an ordinary entry in `generators`, fro
 | `docsFile()` | `docs` | the neutral model surface — one page per entity and per template (`<Entity>.md`, `<Template>.md`), plus an overview with the whole-model ER diagram. Options: `apiSurfaces`, `templates`. |
 | `apiDocsFile()` | `api-docs` | the api reference — `api/<Entity>.md`, `api/README.md`, `api/AGENT-API.md`: the concrete imports, signatures, payload field shapes and runnable examples for THIS project's generated code. Options: `subDir` (default `api`), `modelBaseUrl`. |
 | `requirementsFile()` | `requirements` | the declared `requirement.*` ledger, each entry headed by its dotted path and `title`. Writes nothing for a model with no `requirement.*` node. |
-| `agentDocsFile()` | `agent-docs` | `agent/schema.md`, `agent/ui.md` (only when the run also lists a client-tier generator, OR the config sets `includeUiTier: true` — the escape hatch for a docs-only config whose UI is generated by a separate config; skipping it with a UI surface in the model prints an advisory naming `includeUiTier`) and `agent/requirements.md` — the three `agent/` pages the always-on pointer reads before touching a tier. |
+| `agentDocsFile()` | `agent-docs` | `agent/schema.md`, `agent/ui.md` (only when the run also lists a client-tier generator, OR the config sets `includeUiTier: true` — the escape hatch for a docs-only config whose UI is generated by a separate config; skipping it with a UI surface in the model and `includeUiTier` unset prints an advisory naming `includeUiTier`; `includeUiTier: false` says there is no UI anywhere and skips it without one) and `agent/requirements.md` — the three `agent/` pages the always-on pointer reads before touching a tier. |
 | `metamodelDocsFile()` | `metamodel-docs` | the built-in vocabulary reference, under `metamodel/` (was `meta docs --metamodel`). |
 | `docsSiteFile()` | `docs-site` | an HTML site under `site/` (was `meta docs --site`). Option: `prompts`. `meta eject docs-site` copies its templates and assets to `codegen/docs-site/` (was `meta docs --scaffold-site`). |
 
 
@@ -314,14 +314,16 @@ export const agentDocsFile = function agentDocsFile(opts?: AgentDocsFileOpts): G
         if (ui !== "") {
           if (ctx.config.includeUiTier === true) {
             files.push({ path: `${dir}/ui.md`, content: ui });
-          } else {
+          } else if (ctx.config.includeUiTierExplicit !== true) {
             // The model HAS a UI surface (renderAgentUiPage returned content) but this
-            // run has no client UI generator and no `includeUiTier: true` override, so the
-            // page is skipped. Before this, that was silent: `meta gen` exited 0 and listed
-            // only the pages it wrote, and a docs-only project (its own config generates no
-            // UI; a SEPARATE config does) lost `agent/ui.md` with no signal at all.
+            // run has no client UI generator and the config left `includeUiTier` unset, so
+            // the page is skipped. Before this, that was silent: `meta gen` exited 0 and
+            // listed only the pages it wrote, and a docs-only project (its own config
+            // generates no UI; a SEPARATE config does) lost `agent/ui.md` with no signal at
+            // all. An explicit `includeUiTier: false` says there is no UI anywhere, so a
+            // server-only project has a way to say so and is not advised on every run.
             ctx.warn(
-              `${dir}/ui.md not written: no client UI generator in this run; set includeUiTier: true if another config generates the UI.`,
+              `${dir}/ui.md not written: no client UI generator in this run; set includeUiTier: true if another config generates the UI, or includeUiTier: false if there is no UI.`,
             );
           }
         }
 
@@ -77,6 +77,11 @@ export interface ResolvedGenConfig {
    *  `agent/ui.md` reads this to decide whether a UI tier exists to describe;
    *  a metadata predicate can only say a UI *could* be generated. Undefined ⇒ false. */
   includeUiTier?: boolean;
+  /** Whether `includeUiTier` came from the config rather than from the marker
+   *  aggregation. An explicit `false` means "no UI anywhere", so `agent/ui.md` skips the
+   *  page without advising; an unset key that resolved to `false` still advises.
+   *  Set by the runner only. Undefined ⇒ false. */
+  includeUiTierExplicit?: boolean;
   /**
    * FR-019 / ADR-0026: the module specifier from which an externally-PROVIDED
    * shared enum (`@provided: true` on an abstract package-level `field.enum`) is
@@ -104,7 +109,7 @@ export const DEFAULT_EXT_STYLE: ExtStyle = "js";
  * fills inert defaults when they are absent AND the model emits no DB artifacts, and
  * throws a clear error when they are absent but the model DOES emit DB code (#194).
  */
-export interface MetaobjectsGenConfig extends Omit<ResolvedGenConfig, "dbImport" | "dialect" | "extStyle" | "routesExpose"> {
+export interface MetaobjectsGenConfig extends Omit<ResolvedGenConfig, "dbImport" | "dialect" | "extStyle" | "routesExpose" | "includeUiTierExplicit"> {
   dbImport?: string;
   dialect?: Dialect;
   /** Import-specifier suffix in generated code. Defaults to `"js"` (`./x.js`), which is
 
@@ -40,16 +40,16 @@ const PROMPT_GENERATOR_NAMES: ReadonlySet<string> = new Set([
 export function warnMissingPromptGenerators(
   root: MetaData,
   generators: readonly Generator[],
-  isDocsTarget: (g: Generator) => boolean,
+  writesDocs: (g: Generator) => boolean,
   warn: (msg: string) => void,
 ): void {
   // A run that lists no generator at all, or where every listed generator writes
-  // documentation (its RESOLVED output target — the same per-generator signal
-  // runner.ts's targetOf() uses to place output, not a name match), emitted no code of
-  // any kind. There is nothing for a prompt generator to be missing FROM: telling such a
-  // run to add promptRender() is wrong advice (it would add TypeScript render code to a
-  // project that only writes documentation), so the gate does not fire.
-  if (generators.length === 0 || generators.every(isDocsTarget)) return;
+  // documentation (runner.ts decides that from the generator's registry layer, so a docs
+  // generator on a custom target still counts), emitted no code of any kind. There is
+  // nothing for a prompt generator to be missing FROM: telling such a run to add
+  // promptRender() is wrong advice (it would add TypeScript render code to a project that
+  // only writes documentation), so the gate does not fire.
+  if (generators.length === 0 || generators.every(writesDocs)) return;
   if (generators.some((g) => PROMPT_GENERATOR_NAMES.has(g.name))) return;
 
   // ADR-0039: resolving children — a template may arrive through an overlay or extends.
 
@@ -325,14 +325,16 @@ export const agentDocsFile = function agentDocsFile(opts?: AgentDocsFileOpts): G
         if (ui !== "") {
           if (ctx.config.includeUiTier === true) {
             files.push({ path: `${dir}/ui.md`, content: ui });
-          } else {
+          } else if (ctx.config.includeUiTierExplicit !== true) {
             // The model HAS a UI surface (renderAgentUiPage returned content) but this
-            // run has no client UI generator and no `includeUiTier: true` override, so the
-            // page is skipped. Before this, that was silent: `meta gen` exited 0 and listed
-            // only the pages it wrote, and a docs-only project (its own config generates no
-            // UI; a SEPARATE config does) lost `agent/ui.md` with no signal at all.
+            // run has no client UI generator and the config left `includeUiTier` unset, so
+            // the page is skipped. Before this, that was silent: `meta gen` exited 0 and
+            // listed only the pages it wrote, and a docs-only project (its own config
+            // generates no UI; a SEPARATE config does) lost `agent/ui.md` with no signal at
+            // all. An explicit `includeUiTier: false` says there is no UI anywhere, so a
+            // server-only project has a way to say so and is not advised on every run.
             ctx.warn(
-              `${dir}/ui.md not written: no client UI generator in this run; set includeUiTier: true if another config generates the UI.`,
+              `${dir}/ui.md not written: no client UI generator in this run; set includeUiTier: true if another config generates the UI, or includeUiTier: false if there is no UI.`,
             );
           }
         }