Correct capability documentation and exclude compiler caches from releases

docs/agent-integrations.md

@@ -236,4 +236,4 @@ The additional MCP tools retain the same API contracts:
 | Mediated search | `get_internet_search_configuration`, `configure_internet_search`, `test_internet_search`, `search_internet`, `get_search_citation` |
 | Recorded browser image | `get_browser_evidence_image` |
 
-`configure_internet_search` takes a private key-file path on the **MCP host**, rather than a model-visible key, or an explicit `clear_secret`. The factory server receives the key through its authenticated write-only configuration API. `get_browser_evidence_image` returns native MCP image content from an existing authenticated capture. The Forge transport remains stdio; these tools do not create a public HTTP MCP connector.
+`configure_internet_search` takes a private key-file path on the **MCP host**, rather than a model-visible key, or an explicit `clear_secret`. The factory server receives the key through its authenticated write-only configuration API. `get_browser_evidence_image` returns native MCP image content from an existing authenticated capture. The forge transport remains stdio; these tools do not create a public HTTP MCP connector.

docs/assistant-files.md

@@ -40,7 +40,7 @@ Image bytes are passed as multimodal content to the model. Their receipts record
 
 If an upload loses its reply, refresh the saved-file list before retrying. An exact retry uses the original request ID, filename and content and returns the same receipt. Changing the filename or bytes under that request ID is rejected. The UI keeps the pending file available for an explicit retry.
 
-For a model response with an uncertain outcome, inspect the retained turn and its journal before sending again. Reusing the request ID requires the same message and file selection. Forge does not automatically repeat an uncertain model request.
+For a model response with an uncertain outcome, inspect the retained turn and its journal before sending again. Reusing the request ID requires the same message and file selection. forge does not automatically repeat an uncertain model request.
 
 Each active turn has a persisted owner, an ownership epoch and a renewable lease measured against PostgreSQL's clock. Reading it from another API instance leaves the active request alone. If the lease expires, an authorized editor can explicitly recover that epoch for reconciliation. Recovery fences late replies and records the observed expiry; it does not repeat the model call. See [Conversation recovery](recovery.md#recover-a-product-conversation).
 

docs/brand.md

@@ -7,7 +7,7 @@ description: Use firefly forge logos, Manrope typography and licensed brand asse
 # Use firefly forge visual assets
 
 The product name is **firefly forge**, in lowercase. Its identity combines the
-unmodified Firefly parent artwork, a measured hairline separator and a Forge
+unmodified Firefly parent artwork, a measured hairline separator and a forge
 wordmark with an original lowercase **f** emblem. The factory scene comes from
 the actual Firefly website geometry, rather than a separate flowchart style.
 
@@ -60,7 +60,7 @@ SVG box to the shared shell grid, not a hand-typed product title.
 onboarding composition: projected machines, module platforms, connected
 conveyors, side lane, and separate API/event backbone pipes. Only material
 colors change between themes. Website business-step numbers and decision badges
-are omitted so they do not imply a Forge runtime operation.
+are omitted so they do not imply a forge runtime operation.
 
 The authoritative renderer is `src/scripts/factory-drawing.ts` in
 `firefly-oss/firefly-software-website`, pinned to
@@ -126,7 +126,7 @@ than flattening to a single color. Communicate status in text as well as color.
 revisions and SHA-256 values for generated assets and application copies. Keep
 `NOTICE` with the marks, `OFL.txt` with fonts and the icon notices with their
 bundles. The separate Agent Bridge uses its own connected-span
-identity; its assets are not part of the public Forge inventory.
+identity; its assets are not part of the public forge inventory.
 
 ## Regenerate and review
 

docs/bridge.md

@@ -7,7 +7,7 @@ description: Connect forge to a local Firefly Agent Bridge for development testi
 
 Firefly Agent Bridge runs on the machine with your official Codex or Claude Code subscription login. Get its source and installation instructions from the
 [Firefly Agent Bridge repository](https://github.com/fireflyframework/firefly-agent-bridge).
-Install and operate it separately from Forge, then issue a scoped bridge token for the factory's application connection. Bridge execution is intended for local development and testing; provider account terms and subscription limits still apply.
+Install and operate it separately from forge, then issue a scoped bridge token for the factory's application connection. Bridge execution is intended for local development and testing; provider account terms and subscription limits still apply.
 
 forge includes a client connection to an OpenAI-compatible bridge endpoint.
 The bridge runs separately and authenticates its own clients. Configure the
@@ -32,7 +32,7 @@ The catalog distinguishes configured access from a successful connection test. T
 endpoint rejects a request, inspect the run error and ask the bridge operator
 to verify the authorized configuration.
 
-Forge also supports direct [Codex, Claude Code and native Firefly Agentic](agents.md) connections. Choose the provider and execution boundary that meet the project's requirements.
+forge also supports direct [Codex, Claude Code and native Firefly Agentic](agents.md) connections. Choose the provider and execution boundary that meet the project's requirements.
 
 ## Verify image input for the selected configuration
 

docs/design-review.md

@@ -4,7 +4,7 @@ description: Review wireframes by customer journey and retain approved design re
 
 # Review customer journey wireframes
 
-Generate references before implementation so customers and developers can check each journey, its acceptance criteria, and the shared layout. Forge renders a deterministic wireframe from the current product definition and project brand kit. The result is a review template, not an AI-generated finished product or proof of final visual acceptance.
+Generate references before implementation so customers and developers can check each journey, its acceptance criteria, and the shared layout. forge renders a deterministic wireframe from the current product definition and project brand kit. The result is a review template, not an AI-generated finished product or proof of final visual acceptance.
 
 The product wizard shows every journey at desktop and mobile sizes in light and dark themes. Review all four frames for every screen before acknowledging the bundle. If the customer definition, reviewed architecture, or project brand changes, generate and review a new bundle.
 
@@ -46,7 +46,7 @@ Add this metadata to the unchanged definition, using the actual returned digest
 }
 ```
 
-This is an excerpt to merge into the full product definition, not a standalone product save request. Save through `PUT /api/v1/repositories/{repository_id}/product`. Forge checks that the immutable saved bundle belongs to that repository, matches the definition and current brand digest, and includes all screens, viewports, and themes. Invented digests, missing references, duplicate screen attestations, and stale reviews are rejected.
+This is an excerpt to merge into the full product definition, not a standalone product save request. Save through `PUT /api/v1/repositories/{repository_id}/product`. forge checks that the immutable saved bundle belongs to that repository, matches the definition and current brand digest, and includes all screens, viewports, and themes. Invented digests, missing references, duplicate screen attestations, and stale reviews are rejected.
 
 Existing brief-only workflows can omit `design_review`. The product wizard requires the reference acknowledgement before its final product save. Acknowledgement records the operator's review; it does not replace accessibility testing or a customer's acceptance of the implemented application.
 
@@ -64,7 +64,7 @@ Inspect the actual application separately at wide and narrow widths, both themes
 
 The product definition carries a typed, editable `visual_design` contract. Each product saves its own settings; references freeze those values together with the product's brand digest. Logical project components may inherit their project's canonical product definition. Factory interface settings do not change customer products.
 
-Defaults use a 4 px spacing baseline, 12 desktop columns with 24 px gutters and 32 px outer margins, and four mobile columns with 16 px gutters and 20 px margins. The desktop shell defaults to a 76 px header, 248 px rail and 64 px footer. Reference canvases default to 1440 × 900 and 390 × 844 px. The preview is a review template for the customer product; it does not reproduce the Forge portal or claim to be a finished interface.
+Defaults use a 4 px spacing baseline, 12 desktop columns with 24 px gutters and 32 px outer margins, and four mobile columns with 16 px gutters and 20 px margins. The desktop shell defaults to a 76 px header, 248 px rail and 64 px footer. Reference canvases default to 1440 × 900 and 390 × 844 px. The preview is a review template for the customer product; it does not reproduce the forge portal or claim to be a finished interface.
 
 | Product setting | Supported values |
 | --- | --- |

docs/learning.md

@@ -5,7 +5,7 @@ description: Understand scoped learning, knowledge-first lookup, failed-attempt
 <!-- Copyright 2026 Firefly Software Foundation. SPDX-License-Identifier: Apache-2.0 -->
 # Learn from evidence and reuse knowledge safely
 
-A useful lesson explains which question it addresses, what was observed and where that observation still applies. Forge already retrieves required flycanon context and retains verified repository memory. The learning subsystem adds deterministic eligibility, exact question-to-evidence associations and controls for repeating an unchanged repair attempt.
+A useful lesson explains which question it addresses, what was observed and where that observation still applies. forge already retrieves required flycanon context and retains verified repository memory. The initial learning implementation adds deterministic eligibility and exact question-to-evidence associations. Repeat-control rules remain a pure contract awaiting runtime integration.
 
 !!! info "Implementation boundary"
     The initial learning slice implements scoped PostgreSQL records, evidence eligibility, native knowledge-first decisions and explicit flycanon projection. Local qualification includes an actual indexed source, citation and local embedding, with repeat submission creating no duplicate. Automatic retrieval from projected learning namespaces, classified negative repair circuits, a complete Studio learning workflow and sharing between projects remain open. Generic failed checks record an observed outcome; they do not prove that an approach fails everywhere.
@@ -24,7 +24,7 @@ Learning policy applies to new runs; admitted runs retain their captured policy.
 }
 ```
 
-The values shown are defaults. Disabling the policy affects later admissions. Required framework knowledge remains a separate setting and can still block generation when unavailable.
+The values shown are defaults. The repeated-attempt setting belongs to the pure repair-control contract and is not enforced by the worker repair loop. Existing repair and clarification budgets still govern execution. Disabling the policy affects later admissions. Required framework knowledge remains a separate setting and can still block generation when unavailable.
 
 | Action | CLI command | Factory MCP tool |
 | --- | --- | --- |
@@ -103,7 +103,7 @@ A negative record says that an observed command or check failed in an exact cont
 
 ## Bound repairs while preserving independent QA
 
-An attempt fingerprint identifies the repository/component, exact source tree, dependency context, command and bounded outcome evidence. Repeat control applies to repair generation. If the worker proposes the same failed attempt without changing its context, the orchestrator can hold that attempt and request a different approach or an authorized override.
+An attempt fingerprint identifies the repository/component, exact source tree, dependency context, command and bounded outcome evidence. The pure repeat-control rules apply to repair-generation proposals and preserve independent verification. They are not yet wired into the orchestrator's repair loop. Holding an unchanged failed attempt or requesting an authorized override still requires that integration and its qualification.
 
 Independent final verification still runs. Diagnostics, intentional RED tests and regression checks retain an explicit purpose and cannot be skipped because a previous failure exists. Existing repair and clarification budgets continue to limit execution. A known failure is useful input for the next implementation decision; it cannot substitute for current QA.
 

docs/release-notes.md

@@ -88,7 +88,7 @@ profiles. Angular, React, Next.js and Vue are selectable frontend contracts.
   the provider and preserves each attempt's results.
 - Final passing verification tied to a source-tree snapshot, checked again
   before publication, plus exclusive service ownership of each data directory.
-- Token protection across the Forge API, with native management/admin/actuator
+- Token protection across the forge API, with native management/admin/actuator
   surfaces disabled in the packaged pyfly configuration.
 - Firefly branding, self-hosted typography, accessible SVG diagrams and
   task-based installation, product, integration and operations guides.
@@ -99,7 +99,7 @@ The configured factory gate covers Python tests, lint, formatting and types;
 Studio types, lint, formatting, unit tests, browser journeys and production
 build; and strict MkDocs compilation.
 
-Studio was also exercised against the real authenticated Forge API: connection,
+Studio was also exercised against the real authenticated forge API: connection,
 repository and run creation, cancellation, run diff and verification evidence,
 an actual ZIP download and the product form. Direct browser review covered 1440,
 640, 390 and 360 pixel widths without