scottconverse · Nov 5, 2026 · Nov 5, 2026
diff --git a/README.md b/README.md
@@ -1,6 +1,6 @@
-Windows x64 Beta 1 · MSI 1.7.0.1
+Windows x64 Beta 1 · MSI 1.7.1.1
 
-The signed [Windows x64 beta 1.7.0.1](https://github.com/townlight/townlight/releases/tag/townlight-beta-1-windows-1.7.0.1) passed the documented fresh Windows Sandbox checks with synthetic data.
+The signed [Windows x64 beta 1.7.1.1](https://github.com/townlight/townlight/releases/tag/townlight-v1.7.1-beta.1) passed the documented fresh Windows Sandbox checks with synthetic data.
 
 - <a href="https://townlight.github.io/manuals/core.html#townlight-core-manual" id="toc-townlight-core-manual">Townlight Core Manual</a>
   - <a href="https://townlight.github.io/manuals/core.html#contents" id="toc-contents">Contents</a>
@@ -61,20 +61,20 @@ Staff should begin with First run and Daily workflow. Administrators should also
 | Identity | Value |
 |----|----|
 | Documentation | Townlight Beta 1 naming, Access and Notice candidate |
-| Intended installer version | 1.7.0.1 |
+| Intended installer version | 1.7.1.1 |
 | Product component | townlight-core 1.3.0.dev2 |
 | Principal import package | townlight_core |
-| Native desktop source version | 1.7.0-1 |
-| Candidate hashes | [SHA-256 checksums](https://github.com/townlight/townlight/releases/download/townlight-beta-1-windows-1.7.0.1/SHA256SUMS-Windows-1.7.0.1.txt) and [Windows acceptance summary](https://github.com/townlight/townlight/releases/download/townlight-beta-1-windows-1.7.0.1/ACCEPTANCE-Windows-1.7.0.1.md) |
+| Native desktop source version | 1.7.1-1 |
+| Candidate hashes | [SHA-256 checksums](https://github.com/townlight/townlight/releases/download/townlight-v1.7.1-beta.1/SHA256SUMS-Windows-1.7.1.1.txt) and [Windows acceptance summary](https://github.com/townlight/townlight/releases/download/townlight-v1.7.1-beta.1/ACCEPTANCE-Windows-1.7.1.1.md) |
 | Current owned software license | AGPL-3.0-only |
 | Acceptance composition | Fresh Windows x64 profile; inspections-preview; Station configured separately |
 
 Use an empty database and fresh Windows profile. The installer refuses legacy profile initialization. The approved profile path is `%LOCALAPPDATA%\CivicSuite`. Keep existing profiles and backups.
 
 ## First run
 
-1.  Download the signed MSI, matching source companion and checksums from the [public Windows release](https://github.com/townlight/townlight/releases/tag/townlight-beta-1-windows-1.7.0.1).
-2.  Verify the MSI hash and Authenticode publisher before installing on a fresh Windows profile. See the [Windows acceptance summary](https://github.com/townlight/townlight/releases/download/townlight-beta-1-windows-1.7.0.1/ACCEPTANCE-Windows-1.7.0.1.md) for the tested setup.
+1.  Download the signed MSI, matching source companion and checksums from the [public Windows release](https://github.com/townlight/townlight/releases/tag/townlight-v1.7.1-beta.1).
+2.  Verify the MSI hash and Authenticode publisher before installing on a fresh Windows profile. See the [Windows acceptance summary](https://github.com/townlight/townlight/releases/download/townlight-v1.7.1-beta.1/ACCEPTANCE-Windows-1.7.1.1.md) for the tested setup.
 3.  Launch Townlight under the intended named Windows account. Choose the storage folders. Select **Townlight Inspections candidate** (`inspections-preview`) for the bounded desktop composition, including Access and Notice. A narrower default selection will not expose all workspaces.
 4.  Enter the city profile, time zone and contacts. Create the first named local administrator, sign in and choose protected backup storage. **Continue without local AI** is valid for the deterministic workflows.
 5.  Run Health Check and wait for readiness. Open Townlight. In System Health select **Finish Records Migration** to activate the canonical Python/PostgreSQL runtime. Do not fabricate migration receipts or seed accounts.
@@ -243,7 +243,7 @@ Versioned saves use expected prior revision identifiers where defined. Reopen an
 
 ### Capacity and platform statements
 
-This beta has synthetic single-profile workflow evidence. It does not have a published benchmark for concurrent staff capacity, minimum RAM/CPU, large-source limits or a field SLA. Do not turn a developer machine’s specification into a supported minimum. The signed MSI is 2,082,697,216 bytes; allow additional disk for extracted runtime, database, originals, exports, media and backups. Select equipment/storage after sizing those actual workloads.
+This beta has synthetic single-profile workflow evidence. It does not have a published benchmark for concurrent staff capacity, minimum RAM/CPU, large-source limits or a field SLA. Do not turn a developer machine’s specification into a supported minimum. The signed MSI is 2,081,316,864 bytes; allow additional disk for extracted runtime, database, originals, exports, media and backups. Select equipment/storage after sizing those actual workloads.
 
 The exact [runtime payload lock](https://townlight.github.io/reference/runtime-payload-lock.json) records pinned files, sizes and hashes. The [component metadata](https://townlight.github.io/reference/component-metadata.json) records shipped dependency declarations. These references are more precise than a manually copied dependency list. Third-party and historical license notices must accompany their matching payloads.
 
@@ -371,7 +371,7 @@ On failure, record the time, selected composition, component/installer versions
 
 These results come from the identified signed candidate’s fresh normal-profile Sandbox exercise: real native IPC/HTTP/PostgreSQL and selected headless controls. All accounts, source bundles and media were synthetic. The guest install/uninstall and recovery passed, and the owned Sandbox stopped. No host installed application or standalone CivicCast was changed. This documentation task reuses those receipts; it does not claim a new software acceptance run.
 
-See the [Windows acceptance summary](https://github.com/townlight/townlight/releases/download/townlight-beta-1-windows-1.7.0.1/ACCEPTANCE-Windows-1.7.0.1.md) for this MSI. The historical [evidence index](https://townlight.github.io/reference/sandbox-evidence-index.json) applies to its original build.
+See the [Windows acceptance summary](https://github.com/townlight/townlight/releases/download/townlight-v1.7.1-beta.1/ACCEPTANCE-Windows-1.7.1.1.md) for this MSI. The historical [evidence index](https://townlight.github.io/reference/sandbox-evidence-index.json) applies to its original build.
 
 The limits remain: actual city field acceptance and equipment/network commissioning; Station automatic provisioning/SCM commissioning; every UI/role combination; field recognition accuracy; and historical in-place upgrades are not certified. They are not five invented feature requirements. Fresh-install controlled beta handoff remains the accepted scope. This package makes no city-deployment, publication or general-availability claim.
 

diff --git a/README.txt b/README.txt
@@ -1,6 +1,6 @@
-Windows x64 Beta 1 · MSI 1.7.0.1
+Windows x64 Beta 1 · MSI 1.7.1.1
 
-The signed Windows x64 beta 1.7.0.1 passed the documented fresh Windows
+The signed Windows x64 beta 1.7.1.1 passed the documented fresh Windows
 Sandbox checks with synthetic data.
 
 - Townlight Core Manual
@@ -73,10 +73,10 @@ Beta identity
   Identity                         Value
   -------------------------------- -------------------------------------------------------------------------------
   Documentation                    Townlight Beta 1 naming, Access and Notice candidate
-  Intended installer version       1.7.0.1
+  Intended installer version       1.7.1.1
   Product component                townlight-core 1.3.0.dev2
   Principal import package         townlight_core
-  Native desktop source version    1.7.0-1
+  Native desktop source version    1.7.1-1
   Candidate hashes                 SHA-256 checksums and Windows acceptance summary
   Current owned software license   AGPL-3.0-only
   Acceptance composition           Fresh Windows x64 profile; inspections-preview; Station configured separately
@@ -373,7 +373,7 @@ This beta has synthetic single-profile workflow evidence. It does not
 have a published benchmark for concurrent staff capacity, minimum
 RAM/CPU, large-source limits or a field SLA. Do not turn a developer
 machine’s specification into a supported minimum. The signed MSI is
-2,082,697,216 bytes; allow additional disk for extracted runtime,
+2,081,316,864 bytes; allow additional disk for extracted runtime,
 database, originals, exports, media and backups. Select
 equipment/storage after sizing those actual workloads.
 

diff --git a/USER-MANUAL.docx b/USER-MANUAL.docx
diff --git a/USER-MANUAL.md b/USER-MANUAL.md
@@ -1,6 +1,6 @@
-Windows x64 Beta 1 · MSI 1.7.0.1
+Windows x64 Beta 1 · MSI 1.7.1.1
 
-The signed [Windows x64 beta 1.7.0.1](https://github.com/townlight/townlight/releases/tag/townlight-beta-1-windows-1.7.0.1) passed the documented fresh Windows Sandbox checks with synthetic data.
+The signed [Windows x64 beta 1.7.1.1](https://github.com/townlight/townlight/releases/tag/townlight-v1.7.1-beta.1) passed the documented fresh Windows Sandbox checks with synthetic data.
 
 - <a href="https://townlight.github.io/manuals/core.html#townlight-core-manual" id="toc-townlight-core-manual">Townlight Core Manual</a>
   - <a href="https://townlight.github.io/manuals/core.html#contents" id="toc-contents">Contents</a>
@@ -61,20 +61,20 @@ Staff should begin with First run and Daily workflow. Administrators should also
 | Identity | Value |
 |----|----|
 | Documentation | Townlight Beta 1 naming, Access and Notice candidate |
-| Intended installer version | 1.7.0.1 |
+| Intended installer version | 1.7.1.1 |
 | Product component | townlight-core 1.3.0.dev2 |
 | Principal import package | townlight_core |
-| Native desktop source version | 1.7.0-1 |
-| Candidate hashes | [SHA-256 checksums](https://github.com/townlight/townlight/releases/download/townlight-beta-1-windows-1.7.0.1/SHA256SUMS-Windows-1.7.0.1.txt) and [Windows acceptance summary](https://github.com/townlight/townlight/releases/download/townlight-beta-1-windows-1.7.0.1/ACCEPTANCE-Windows-1.7.0.1.md) |
+| Native desktop source version | 1.7.1-1 |
+| Candidate hashes | [SHA-256 checksums](https://github.com/townlight/townlight/releases/download/townlight-v1.7.1-beta.1/SHA256SUMS-Windows-1.7.1.1.txt) and [Windows acceptance summary](https://github.com/townlight/townlight/releases/download/townlight-v1.7.1-beta.1/ACCEPTANCE-Windows-1.7.1.1.md) |
 | Current owned software license | AGPL-3.0-only |
 | Acceptance composition | Fresh Windows x64 profile; inspections-preview; Station configured separately |
 
 Use an empty database and fresh Windows profile. The installer refuses legacy profile initialization. The approved profile path is `%LOCALAPPDATA%\CivicSuite`. Keep existing profiles and backups.
 
 ## First run
 
-1.  Download the signed MSI, matching source companion and checksums from the [public Windows release](https://github.com/townlight/townlight/releases/tag/townlight-beta-1-windows-1.7.0.1).
-2.  Verify the MSI hash and Authenticode publisher before installing on a fresh Windows profile. See the [Windows acceptance summary](https://github.com/townlight/townlight/releases/download/townlight-beta-1-windows-1.7.0.1/ACCEPTANCE-Windows-1.7.0.1.md) for the tested setup.
+1.  Download the signed MSI, matching source companion and checksums from the [public Windows release](https://github.com/townlight/townlight/releases/tag/townlight-v1.7.1-beta.1).
+2.  Verify the MSI hash and Authenticode publisher before installing on a fresh Windows profile. See the [Windows acceptance summary](https://github.com/townlight/townlight/releases/download/townlight-v1.7.1-beta.1/ACCEPTANCE-Windows-1.7.1.1.md) for the tested setup.
 3.  Launch Townlight under the intended named Windows account. Choose the storage folders. Select **Townlight Inspections candidate** (`inspections-preview`) for the bounded desktop composition, including Access and Notice. A narrower default selection will not expose all workspaces.
 4.  Enter the city profile, time zone and contacts. Create the first named local administrator, sign in and choose protected backup storage. **Continue without local AI** is valid for the deterministic workflows.
 5.  Run Health Check and wait for readiness. Open Townlight. In System Health select **Finish Records Migration** to activate the canonical Python/PostgreSQL runtime. Do not fabricate migration receipts or seed accounts.
@@ -243,7 +243,7 @@ Versioned saves use expected prior revision identifiers where defined. Reopen an
 
 ### Capacity and platform statements
 
-This beta has synthetic single-profile workflow evidence. It does not have a published benchmark for concurrent staff capacity, minimum RAM/CPU, large-source limits or a field SLA. Do not turn a developer machine’s specification into a supported minimum. The signed MSI is 2,082,697,216 bytes; allow additional disk for extracted runtime, database, originals, exports, media and backups. Select equipment/storage after sizing those actual workloads.
+This beta has synthetic single-profile workflow evidence. It does not have a published benchmark for concurrent staff capacity, minimum RAM/CPU, large-source limits or a field SLA. Do not turn a developer machine’s specification into a supported minimum. The signed MSI is 2,081,316,864 bytes; allow additional disk for extracted runtime, database, originals, exports, media and backups. Select equipment/storage after sizing those actual workloads.
 
 The exact [runtime payload lock](https://townlight.github.io/reference/runtime-payload-lock.json) records pinned files, sizes and hashes. The [component metadata](https://townlight.github.io/reference/component-metadata.json) records shipped dependency declarations. These references are more precise than a manually copied dependency list. Third-party and historical license notices must accompany their matching payloads.
 
@@ -371,7 +371,7 @@ On failure, record the time, selected composition, component/installer versions
 
 These results come from the identified signed candidate’s fresh normal-profile Sandbox exercise: real native IPC/HTTP/PostgreSQL and selected headless controls. All accounts, source bundles and media were synthetic. The guest install/uninstall and recovery passed, and the owned Sandbox stopped. No host installed application or standalone CivicCast was changed. This documentation task reuses those receipts; it does not claim a new software acceptance run.
 
-See the [Windows acceptance summary](https://github.com/townlight/townlight/releases/download/townlight-beta-1-windows-1.7.0.1/ACCEPTANCE-Windows-1.7.0.1.md) for this MSI. The historical [evidence index](https://townlight.github.io/reference/sandbox-evidence-index.json) applies to its original build.
+See the [Windows acceptance summary](https://github.com/townlight/townlight/releases/download/townlight-v1.7.1-beta.1/ACCEPTANCE-Windows-1.7.1.1.md) for this MSI. The historical [evidence index](https://townlight.github.io/reference/sandbox-evidence-index.json) applies to its original build.
 
 The limits remain: actual city field acceptance and equipment/network commissioning; Station automatic provisioning/SCM commissioning; every UI/role combination; field recognition accuracy; and historical in-place upgrades are not certified. They are not five invented feature requirements. Fresh-install controlled beta handoff remains the accepted scope. This package makes no city-deployment, publication or general-availability claim.
 

diff --git a/USER-MANUAL.pdf b/USER-MANUAL.pdf
diff --git a/USER-MANUAL.txt b/USER-MANUAL.txt
@@ -1,6 +1,6 @@
-Windows x64 Beta 1 · MSI 1.7.0.1
+Windows x64 Beta 1 · MSI 1.7.1.1
 
-The signed Windows x64 beta 1.7.0.1 passed the documented fresh Windows
+The signed Windows x64 beta 1.7.1.1 passed the documented fresh Windows
 Sandbox checks with synthetic data.
 
 - Townlight Core Manual
@@ -73,10 +73,10 @@ Beta identity
   Identity                         Value
   -------------------------------- -------------------------------------------------------------------------------
   Documentation                    Townlight Beta 1 naming, Access and Notice candidate
-  Intended installer version       1.7.0.1
+  Intended installer version       1.7.1.1
   Product component                townlight-core 1.3.0.dev2
   Principal import package         townlight_core
-  Native desktop source version    1.7.0-1
+  Native desktop source version    1.7.1-1
   Candidate hashes                 SHA-256 checksums and Windows acceptance summary
   Current owned software license   AGPL-3.0-only
   Acceptance composition           Fresh Windows x64 profile; inspections-preview; Station configured separately
@@ -373,7 +373,7 @@ This beta has synthetic single-profile workflow evidence. It does not
 have a published benchmark for concurrent staff capacity, minimum
 RAM/CPU, large-source limits or a field SLA. Do not turn a developer
 machine’s specification into a supported minimum. The signed MSI is
-2,082,697,216 bytes; allow additional disk for extracted runtime,
+2,081,316,864 bytes; allow additional disk for extracted runtime,
 database, originals, exports, media and backups. Select
 equipment/storage after sizing those actual workloads.
 

diff --git a/docs/beta-1/api/access.html b/docs/beta-1/api/access.html
@@ -8,7 +8,7 @@
 @media print{html{scroll-behavior:auto}body{font:10.5pt/1.45 Arial,sans-serif;color:#172f39}header,footer,.search-area,.screen-only{display:none}.doclayout{display:block;padding:0;max-width:none}.toc{position:static;max-height:none;overflow:visible;font-size:10pt;break-after:page}.toc>h2{border:0}.toc ul{columns:2;column-gap:.3in}.toc li{break-inside:avoid}.docbody h1{font-size:30pt}.docbody h2{font-size:19pt;break-after:avoid;padding-top:.15in;margin-top:.35in}.docbody h3{font-size:12pt;break-after:avoid}.docbody h4{break-after:avoid}p{orphans:3;widows:3}pre{font-size:8.2pt;line-height:1.4;padding:.1in;break-inside:auto}table{font-size:8.4pt;line-height:1.35}th,td{padding:.06in .07in}tr{break-inside:avoid}.flow{max-height:6in;object-fit:contain;break-inside:avoid}a{color:#172f39;text-decoration:underline}.cover{break-after:page;padding-top:1in}.cover .edition{font-size:11pt}.cover h1{font-size:32pt}.cover .lead{font-size:14pt}.api-entry{break-inside:auto}.api-entry h3{break-after:avoid}.index-columns{columns:2}}
 
 pre{white-space:pre-wrap;overflow-wrap:anywhere}summary{cursor:pointer;padding:.6rem;font-weight:600}details{margin:.5rem 0}</style></head><body><a class="skip" href="#main">Skip to content</a><header><a class="brand" href="../index.html">Townlight</a><nav aria-label="Main"><a href="../manuals/suite.html">Suite manual</a><a href="../versions.html">Versions and release</a><a href="../reference/index.html">Technical reference</a></nav></header><main class="reading wrap" id="main"><h1>Townlight Access API reference</h1>
-<p>Windows Beta 1 · source reference. The signed <a href="https://github.com/townlight/townlight/releases/tag/townlight-beta-1-windows-1.7.0.1">Windows x64 beta 1.7.0.1</a> passed the documented fresh Windows Sandbox checks with synthetic data. This schema describes source contracts. The <a href="https://github.com/townlight/townlight/releases/download/townlight-beta-1-windows-1.7.0.1/ACCEPTANCE-Windows-1.7.0.1.md">Windows acceptance summary</a> identifies the installed checks.</p>
+<p>Windows Beta 1 · source reference. The signed <a href="https://github.com/townlight/townlight/releases/tag/townlight-v1.7.1-beta.1">Windows x64 beta 1.7.1.1</a> passed the documented fresh Windows Sandbox checks with synthetic data. This schema describes source contracts. The <a href="https://github.com/townlight/townlight/releases/download/townlight-v1.7.1-beta.1/ACCEPTANCE-Windows-1.7.1.1.md">Windows acceptance summary</a> identifies the installed checks.</p>
 <p>Townlight Access 0.5.0. The HTTP host is Townlight Records 1.8.0.dev2. Component package versions and the host API version are separate identities.</p>
 <p>Generated from the actual native inspections-preview composition without application lifespan, migrations or database/network access. It describes route and validation contracts; it does not establish endpoint behavior, individual authorization or installed acceptance. Standalone product applications have separate deployment boundaries.</p>
 <p><a href="access-openapi.json">Machine-readable OpenAPI schema</a> · <a href="../manuals/access.html">Operating manual and limits</a></p>