v1.3.0 - Stable rebuilt line

v1.3.0 - Stable rebuilt line

First Stable Release

v1.3.0 is the first stable release of the rebuilt line. It brings together the
safer upgrades from 9024, the default-settings fixes from 9025, and the new quick
upgrade guide. Technical and research commands, adapters, and skills remain
available. Installing, updating, and linking do not require Kilo.

Upgrade

Follow the Windows and macOS upgrade guide
for older installations, fresh installs, project refresh, and removal.

On v1.2.0.9024 or newer, run this from your home folder, not a project:

cg-update v1.3.0

Open a new terminal. In each project, keep its adapter selection with
--platforms on both NEW cg-link commands. For a Copilot-only project:

cg-link --check --platforms copilot
cg-link --platforms copilot

Without --platforms, every adapter is linked. Review any reported manual
action. Use the explicit version: cg-update latest follows main, not the
GitHub Latest release.

On older versions, follow the guide's one-time migration using a fresh
v1.3.0 clone. Keep the old installation backup and the printed rollback
command. Do not run the old updater or linker first.

Safer Project Refresh

• Migration keeps the old installation in a sibling backup, installs at the
  original path, and pins the chosen version.
• cg-link --check is read-only. Edited, unowned, and user-added files are
  preserved for review rather than silently replaced.
• The one-time legacy Copilot instructions transition saves original bytes in
  .github/copilot-instructions.md.pre-9024.bak. Review and merge your custom
  instructions from that backup.
• PATH warnings explain how to use the new installation instead of an old
  command that takes precedence.
• Older compound-gpid.local.md files containing notes but no settings block
  use defaults; an initial UTF-8 BOM is accepted. Your file is not rewritten.
  Run /cg-setup later if you need settings.
• Repeated linking removes duplicate managed .gitignore entries and obsolete
  internal copies.

Tested Coverage

Windows and macOS CI fixtures cover migration from v1.1.11 and
v1.2.0.9021, updates through the installed 9024 updater, older-updater
recovery, and the published quick-guide commands. They check backups, preserved
user files, default settings, pins, read-only checks, and repeat linking.
Required gates also run native Python and Pester tests on both platforms.

These are isolated fixtures, not proof for every historical installation or
a real Kilo host. See the release-preparation PRs and CI workflow runs for
check results.

Known Limits

• Migration supports standalone Git clones, not worktrees or linked installation
  paths. Existing backups or multiple installations can require explicit
  selection or recovery. Local installation edits stay in the backup, not merged.
• Rollback restores the installation, not project changes or every PATH/profile
  write. Keep reviewed project backups.
• Windows PowerShell 5.1 long-path copy/unlink limits remain. Use short
  installation paths; do not remove user files to force success.
• Keep blocked or preserved files and resolve the reported manual action.
  Do not delete adapter folders or use unlink to bypass conflicts.

Publication

Release payload dates identify the payload snapshot, not the GitHub publication
time. See the GitHub release page for publication status and timestamps. The
GitHub Latest designation is managed separately by the owner.

v1.2.0.9025 - Default Settings

v1.2.0.9025 - Default Settings

Default Settings

Older projects could stop at cg-link when compound-gpid.local.md contained
notes but no settings block. cg-link now continues with default settings and
can also read files that start with a UTF-8 BOM. Your file is not changed.
Run /cg-setup later to add settings when you need them.

cg-link no longer adds duplicate .gitignore lines and removes prior duplicates.
cg-link no longer keeps old internal copies under .compound-gpid.

Upgrade To 9025

From v1.2.0.9024 on Windows or macOS, run this outside linked project directories
(for example, from your home directory):

cg-update v1.2.0.9025

Then run the NEW cg-link once per project, keeping its adapter selection. Use
the explicit version, not latest.

From older versions, follow the Windows and macOS Upgrade Guide
to migrate and install v1.2.0.9024 first. Then run cg-update v1.2.0.9025
and the NEW cg-link once per project.

Keep installation and project backups. If linking reports blocked or preserved
files, keep them and review the reported manual action. Do not delete adapter
folders or use unlink to bypass conflicts.

Tests Added

Tests added cover default-settings configuration reads, initial UTF-8 BOM
handling, strict validation errors, read-only checking, and Windows/macOS
upgrade/update fixtures. These are coverage additions, not a claim that local
or hosted gates have passed. They do not qualify every historical installation
or a real Kilo host.

The installed 9024 updater is tested from a neutral directory, followed by the
NEW linker in the original valid-config project and a second legacy-config
project. Running that old updater inside a linked project can stop at its stale
manifest guard; use the neutral-directory update path instead.

Publication

Every four-part vX.Y.Z.N tag is Reserve-only: a non-draft GitHub pre-release
with make_latest=false. No Finalize, documentation deployment, or attestation
applies. Required payload dates are preparation timestamps, not publication
proof. Publication requires green local, push, and FULL CI gates.

v1.2.0.9024 - Safer Upgrades

v1.2.0.9024 - Safer Upgrades

Upgrade From Any Older Version

Pinned and latest users use the same path: clone the official repository at
v1.2.0.9024 into a separate fresh folder, then run the NEW clone's migration
script by full path. Do not run the old updater or linker first.
Migration keeps the old installation in a sibling backup, installs at the
original path, and pins v1.2.0.9024. It does not reconcile projects.

Follow the Windows and macOS Upgrade Guide
for default/custom paths, multiple installations, checks, PATH repair, and rollback.
After migration, open a new terminal and verify cg-link resolves to the new
installation. A PATH warning keeps the verified installation and prints repair
guidance; do not run a shadowing old command.

Stay pinned. Do not run cg-update latest until announced: today latest
tracks main, which still contains the old line, not the newest four-part tag.

Project Files And Notices

Run the NEW cg-link --check, then cg-link in each project, keeping its adapter
selection. The check is read-only: no update, Kilo launch, or project/global
writes. Review blocks or preserved conflicts before linking.

Edited or unproven files are kept and reported as manual action required;
user-added files are kept. Do not delete adapter folders or use unlink to bypass
conflicts. The one-time legacy managed Copilot instructions transition first
saves exact prior bytes to .github/copilot-instructions.md.pre-9024.bak, then
replaces the instructions. Review and merge custom instructions from that backup.
Later replacement needs unchanged ownership proof. Existing conflicting backups
are preserved and need manual action.

The original reveal.js and Marked vendor license notices are restored at
presentation/vendor/reveal.js/LICENSE and LICENSE.marked.txt.

Tested Coverage

CI run 38805538140
passed all four upgrade cells: v1.1.11 and v1.2.0.9021 on Windows and macOS.
Isolated fixtures cover preservation, Copilot backup, read-only checking, and
repeat linking. Real user pilots follow publication. These tests do not prove
every historical version or qualify a real Kilo host.

Known Limits And Rollback

Only standalone Git clones are supported; worktrees and linked installation
paths are refused. Multiple installations need explicit path selection. Existing
backups stop a new migration until inspected and recovered through rollback.
Local installation edits remain in the backup, not merged into the new clone.
Windows PowerShell 5.1 long-path copy/unlink limits remain; use short install paths.

Use the migration script's explicit rollback mode and the exact command it
prints. Rollback restores the old installation and keeps the current one aside.
It does not undo project changes. Installer PATH/profile writes are not
snapshotted; review those manually and restore only reviewed project backups.

Publication

Every four-part vX.Y.Z.N tag is Reserve-only: a non-draft GitHub pre-release
with make_latest=false. No Finalize, documentation deployment, or attestation
applies. Required payload dates are preparation timestamps, not publication
proof. Publication requires green local, push, and FULL CI gates.

v1.2.0.9023 - Kilo-independent installation and updates

v1.2.0.9023 - Kilo Independence

What Changed

Compound GPID install, update, link, and unlink do not run Kilo. They do not
depend on a Kilo version or host behavior. Local validation of generated
Compound GPID files and ownership checks remain.

When Kilo and Claude or Codex skills coexist, a non-blocking note recommends
cg-kilo for contained launches. The optional launcher keeps
KILO_DISABLE_EXTERNAL_SKILLS containment. Old or unreadable Kilo versions
produce warnings, not a version gate.

Upgrade From 9022

1. Open a terminal in a NEW EMPTY FOLDER. Do not use your home folder or a
   Kilo-linked project. The installed 9022 updater still has the old host check.
2. Run cg-update v1.2.0.9023. Stop if it fails. Do not use latest or --fix
   to bypass an error.
3. After success, run the NEW cg-link once in each project. Keep the adapter
   selection used by that project and check each result.

Mac Installs On 9006-9016

Use the same re-clone procedure as 9022, with the 9023 tag:

1. Close tools and terminals that use the installation. Record the original
   path, commit, version pin, and local changes. Back up projects, including
   private configuration and ownership records.
2. Move the old installation clone aside. Keep it outside adapter discovery
   folders; do not delete it or discard local changes.
3. Clone https://github.com/GPID-WB/compound-gpid.git at the SAME original
   installation path. In the new clone, run
   git checkout --detach v1.2.0.9023, then
   printf '%s\n' v1.2.0.9023 > .cg-version.
4. Run bash "<original-install-path>/scripts/install.sh". Stop on failure.
5. Open a new terminal. Check that command -v cg-link points to the new clone.
   Run the NEW cg-link once per project and check each result.

If linking blocks or preserves old files, keep the files, ownership records,
journals, and private configuration. Use reviewed manual repair. Do not delete
an adapter folder or use cg-unlink as a cleanup shortcut.

For rollback, close affected tools, move the new clone aside, and restore the
old clone at its original path. Run its installer and open a new terminal.
Clone rollback does not undo project changes; restore only reviewed backups.
The known 9022 Windows PowerShell 5.1 long-path copy/unlink limits remain.

Publication

Every four-part vX.Y.Z.N tag uses Reserve-only publication: a non-draft
pre-release with make_latest=false. No Finalize, docs deployment, or
attestation applies. Three-part stable tags keep the full path.

Publication is conditional on successful local gates and all applicable push
and FULL CI rows. The payload date is the preparation date, not publication
proof. No real local installation or real Kilo launch is part of this work.

v1.2.0.9022 - Safe-baseline rebuild

v1.2.0.9022 - Safe-Baseline Rebuild

Prepared release notes. This release has not been published. Windows and Mac
pilots and publication approval are pending. The schema-version-1 payload uses
the preparation date, 2026-10-08, in its required date fields; these fields are
not proof of publication.

What 9022 Contains

9022 starts from the v1.2.0.9017 baseline and adds the safety fixes in Slices
1-4a. It keeps ordinary commands, adapters, skills, and the research suite.
The fixes preserve user files when old generated files cannot be proved safe
to remove, ignore private local configuration in Git, recover the original
checkout and version pin after a new pinned update fails validation, correct
Windows Python detection and secure long-path staging, and keep a POSIX
installation clone clean. CI has bounded jobs and fresh install, link, and
unlink smoke fixtures.

This is a small rebuild, not a restoration of every 9020/9021 feature. The
following 9020/9021 features are NOT in 9022:

• cg-help answers and support evidence.
• Docs browser changes.
• Kilo autopilot and the native plugin.
• The async release controller.
• New release-controller receipts.
• Pages sealing.

Baseline ownership records are still used. The omitted receipts do not mean
that existing project ownership records can be deleted. Existing configuration
access and global Kilo permission behavior are unchanged. Git ignore rules do
not prevent configuration access. Hosted fixtures do not qualify a real Kilo
host or certify a user's installation.

Supported Migration: Re-Clone

Use re-clone to migrate from 9020 or 9021. Do not use the old updater for the
supported migration. Before publication, approved pilots must use the exact
candidate commit in the external pilot checklist, not a tag or latest.
The commands below apply only AFTER publication approval and publication.

Windows

1. Close terminals and AI tools that use the installation. Record its full
   path, current commit, version pin, and any local changes. Back up affected
   projects, including private configuration and ownership records.
2. Move the entire old installation clone to a backup path outside project
   adapter folders. Keep it; do not delete it or discard local changes.
3. Clone https://github.com/GPID-WB/compound-gpid.git at the SAME original
   installation path. In that new clone, run
   git checkout --detach v1.2.0.9022. Check that the checkout succeeded. Set
   the new clone's .cg-version to v1.2.0.9022, not latest, before the
   installer: Set-Content -LiteralPath .cg-version -Value v1.2.0.9022 -Encoding ASCII.
4. In PowerShell, run & "<original-install-path>\install.ps1". Do not change
   corporate execution policy to force it to run. Stop if it fails.
5. Open a new terminal. Check that cg-link resolves to the new clone. In each
   project, run the NEW cg-link once, with the adapter selection used by that
   project. Check each result before you continue to another project.

macOS

1. Close terminals and AI tools that use the installation. Record its full
   path, current commit, version pin, and any local changes. Back up affected
   projects, including private configuration and ownership records.
2. Move the entire old installation clone to a backup path outside project
   adapter folders. Keep it; do not delete it or discard local changes.
3. Clone https://github.com/GPID-WB/compound-gpid.git at the SAME original
   installation path. In that new clone, run
   git checkout --detach v1.2.0.9022. Check that the checkout succeeded. Set
   the new clone's .cg-version to v1.2.0.9022, not latest, before the
   installer: printf '%s\n' v1.2.0.9022 > .cg-version.
4. Run bash "<original-install-path>/scripts/install.sh". Stop if it fails.
5. Open a new terminal. Check that command -v cg-link resolves to the new
   clone. In each project, run the NEW cg-link once, with the adapter
   selection used by that project. Check each result before you continue.

If cg-link Blocks Or Preserves Old Plugin Files

Stop on an error or a report that active old plugin files need manual repair.
Do not launch the old plugin between repair steps. Keep old files, ownership
receipts, attestations, journals, locks, and private configuration in place.
Store review copies outside adapter discovery folders. Do not fabricate
ownership, delete journals, recursively remove an adapter folder, or use
cg-unlink as a cleanup shortcut.

Have a maintainer review the exact blocked files and records. Only after
separate manual approval, archive the specific blocked managed units together
with their markers and user content, and perform the reviewed repair. Run NEW
cg-link again only when the cause is resolved. Automatic cleanup of every old
consumer file is not promised. Record preserved files even when linking
succeeds; do not treat a preserved file as safe to delete.

Known Limits

• Windows PowerShell 5.1 still has legacy long-path copy and unlink limits.
  A short installation and test-project path reduces this risk but is not a
  guarantee. Stop on path errors; do not delete or rename user project files
  to force success.
• The unpublished recovery updater is not supported. Maintainers must re-clone.
• Clone rollback does not undo all project changes. Keep project backups and
  review any changed files before you restore them.
• 9022 publication is Reserve-only: a non-draft GitHub pre-release with
  make_latest=false from the exact pushed source branch. It does not deploy
  documentation and has no Pages or Finalize attestation dependency. Other
  release versions retain their existing completion rules.

Advanced Note: Old-Updater Acquisition Is Unsupported

This is maintainer guidance, not the migration procedure above. Old pinned
updaters can leave a changed checkout or version pin after a later failure and
can leave stale copies or mirrors in projects.

Before any separately reviewed old-updater procedure, record the original
commit, branch or detached state, and exact pin bytes or absence. Preserve
staged, user, or unknown edits and stop if they exist. Restore ONLY files proved
to be old installer output, from the old HEAD and under manual review. Never
use a blanket reset, checkout of all files, or --fix to force acquisition.
Use explicit cg-update v1.2.0.9022, never latest, and stop on any error.
Acquisition is not completed migration. Reconcile separately with NEW 9022
cg-link and process-only CG_SKIP_UPDATE=1; unresolved active plugin files or
incompatible journals still require reviewed manual repair.

Rollback

The old clone remains available if 9022 does not work. Stop using the new clone,
close affected terminals and tools, move the new clone aside, and move the old
clone back to its exact original path. Run the old clone's installer and open a
new terminal. Check the old commit, wrapper paths, and version pin. Restore
project files only from reviewed backups. Keep both clones and failure logs
until the result is understood. Do not assume that restoring a clone restores
every project side effect.

v1.2.0.9021 - Routine full releases from dev

What's new

Routine full releases from dev (/cg-release)

The existing PowerShell release workflow now accepts a three-number full release
from a clean, verified dev checkout as well as a four-number prerelease. The tag
shape determines whether GitHub marks the Release as a prerelease; it does not
choose or authorize the source branch. A detached checkout can name its source
with --source-branch dev.

Both release types prepare a reviewed payload, run the commit-bound gate, and
use Reserve to publish the annotated tag and matching GitHub Release before
documentation work. Stable releases keep manual confirmation and manual PR
merges. The separate generic release controller remains disabled. This update
does not remove the publisher's authority, source, or repository-rule checks.

/cg-release v1.2.0 --source-branch dev
/cg-release v1.2.0.9021 --source-branch dev

Bug fixes

• Align the release help catalog with its source digest so command evidence remains verifiable.
• Rebind release support evidence to the integrated dev source after merge.

Under the hood

• Bind the routine release support record used by the help documentation.
• Record the v1.2.0.9020 release attestation on dev.

459 older knowledge entries were outside the scan window and are not included in this release summary.

Upgrading

cg-update

Or pin to this specific release:

cg-update v1.2.0.9021

v1.2.0.9020 - Routine development prereleases

What's new

Routine development prereleases (/cg-release)

Publish a four-number Compound GPID prerelease such as v1.2.0.9020 through the existing PowerShell release workflow. The command prepares a reviewed payload, runs the complete commit-bound gate, reserves an annotated tag and matching GitHub prerelease, checks the exact documentation build, and records release evidence. A verified same-repository branch, including dev, can supply a prerelease. The separate generic release tool remains disabled; this path does not enable it or change the rules for full releases.

An interrupted four-number release can use /cg-release --resume <tag> --source-branch <branch> to reconcile the same tag and release without replacing either one. The publisher checks the current remote policy before consequential steps. Other writers can still change that policy, so this is not an exclusive publication lock.

Find commands and follow workflows (/cg-help)

The new help command uses a reviewed catalog to find Compound GPID commands and explain how to use them. It covers technical and research workflows and checks source evidence before returning a command. Catalog generation and native adapter assets keep the command definitions aligned. Platform support claims remain tied to recorded evidence, not assumed host compatibility.

Read the documentation by task (docs/)

The site now has task-oriented navigation, a command browser, search and reading tools, and separate Published and Development channels. A consolidated Skill Management guide puts related tasks in one place while retaining the detailed references. The site binds displayed content to a verified build and one command-catalog snapshot; mobile navigation and channel handling have corresponding checks.

Kilo-first autopilot foundation (/cg-autopilot)

Add stage-mode workflow contracts, bootstrap agents, bounded evidence checks, and native identity support for a future phased execution workflow. The current command remains in bootstrap and probe mode; it does not enable unattended production execution.

Safer release checks and site previews (scripts/cg_pr_preflight.py)

Commit-bound preflight receipts let the existing publisher verify a completed gate against the exact source tree instead of repeating it without evidence. Development-site previews compose with a verified, durable official-site snapshot rather than treating a moving checkout as the published source. Initial official-snapshot setup still needs a separately authorized deployment.

Bug fixes

• Preserve complete native command arguments and source bindings in help results.
• Confine help support-manifest writes and separate recorded support evidence from live-host assumptions.
• Keep verified page state and build documentation from one catalog snapshot; repair mobile navigation targets.
• Align release-site composition with verified staging and give the full native pytest gate enough time to finish.
• Harden installer, ownership, and generated-target checks across supported adapters.

Under the hood

• Add release, receipt, documentation-snapshot, help, autopilot, installer, and ownership regression coverage.
• Regenerate command and agent assets for the native platform adapters.
• Record the Routine cutover limit and keep the unactivated generic release tool separate from this publication path.

438 older knowledge entries were outside the scan window and are not included in this release summary.

Upgrading

cg-update

Or pin to this specific release:

cg-update v1.2.0.9020

v1.2.0.9019 - Asynchronous Release Controller

What's new

Asynchronous Release Controller (cg-release)

Add a standalone deterministic release controller with plan, start, status, and resume commands. The controller manages release requests through GitHub Issues as a durable admission inbox, maintains a Git journal for state tracking, and publishes from exact reviewed release commits with explicit approval workflows.

Key features:

• Standalone Python package isolated from root scripts
• Strict SemVer ordering with explicit release lines and branch policies
• Plan and start commands read input only, no side effects
• Status and resume commands reconcile from portable request locators
• Disabled publication pending reviewed live setup
• Ordinary PR CI and offline verification included

Bind Release Snapshots to Verified Producer Bytes

Validate stable output identity and per-job Pages authority by composing verified snapshots without executing downloaded source. Register documentation regression gates and build release-snapshot artifacts with complete file inventories and digests included in the release build identity.

Bug fixes

• Raise package matrix timeout to thirty minutes for large dependency tests
• Keep bridge_client within module line limit
• Stop forwarding PowerShell module path into bridge child processes
• Repair release portability and safe diagnostics, preserving private-file checks and offline budgets
• Integrate dev into release controller branch without rewriting PR history

Under the hood

• Capture release validation and authority lessons: clean default dependency gates, executable fixture controls, private GPG socket path limits, and continuation authority boundaries
• Preserve controller history and dev PR handoff documentation
• Record asynchronous controller delivery and live deferral decision (D-2026-09-13-defer-live-rollout)
• Document controller operation, command semantics, authority boundaries, and recovery procedures
• Regenerate release interfaces for Kilo, OpenCode, Codex, and Claude targets
• Verify reader migration and GPID producer contracts with shared Bash fixtures
• Cover controller authority and recovery boundaries in tests
• Accept the new release-docs artifact layout in the Pages deployment verifier
• Read ruleset-based default-branch protection in the legacy release authority

101 older changes were outside the scan window and are not included in this release summary.

Upgrading

cg-update

Or pin to this specific release:

cg-update v1.2.0.9019

v1.2.0.9018 - Asynchronous Release Controller

What's new

Asynchronous Release Controller (cg-release)

Add a standalone deterministic release controller with plan, start, status, and resume commands. The controller manages release requests through GitHub Issues as a durable admission inbox, maintains a Git journal for state tracking, and publishes from exact reviewed release commits with explicit approval workflows.

Key features:

• Standalone Python package isolated from root scripts
• Strict SemVer ordering with explicit release lines and branch policies
• Plan and start commands read input only, no side effects
• Status and resume commands reconcile from portable request locators
• Disabled publication pending reviewed live setup
• Ordinary PR CI and offline verification included

Bind Release Snapshots to Verified Producer Bytes

Validate stable output identity and per-job Pages authority by composing verified snapshots without executing downloaded source. Register documentation regression gates and build release-snapshot artifacts with complete file inventories and digests included in the release build identity.

Bug fixes

• Raise package matrix timeout to thirty minutes for large dependency tests
• Keep bridge_client within module line limit
• Stop forwarding PowerShell module path into bridge child processes
• Repair release portability and safe diagnostics, preserving private-file checks and offline budgets
• Integrate dev into release controller branch without rewriting PR history

Under the hood

• Capture release validation and authority lessons: clean default dependency gates, executable fixture controls, private GPG socket path limits, and continuation authority boundaries
• Preserve controller history and dev PR handoff documentation
• Record asynchronous controller delivery and live deferral decision (D-2026-09-13-defer-live-rollout)
• Document controller operation, command semantics, authority boundaries, and recovery procedures
• Regenerate release interfaces for Kilo, OpenCode, Codex, and Claude targets
• Verify reader migration and GPID producer contracts with shared Bash fixtures
• Cover controller authority and recovery boundaries in tests

101 older changes were outside the scan window and are not included in this release summary.

Upgrading

cg-update

Or pin to this specific release:

cg-update v1.2.0.9018

v1.2.0.9017 - Kilo minimum-version compatibility

Bug fixes

Kilo minimum-version compatibility

Kilo runtime validation now accepts valid versions at or above 7.4.20, including
7.5.16, without an exact-version allowlist or upper bound. This fixes update
and launch failures caused by newer Kilo versions. Malformed and below-minimum
versions remain rejected. Live capability, trust, local projection, no-follow,
and containment checks remain required.

Under the hood

• Added regression tests for minimum-version comparisons and rejected version inputs.
• Updated canonical and generated PR verification guidance: recorded CI host versions and executable hashes are evidence, not consumer version pins.
• Documented recovery for an older installed updater that rejects a newer Kilo version before downloading the fix.
• Recorded and merged the canonical and generated v1.2.0.9016 release attestation through PR #167.

Upgrading

cg-update

Or pin to this specific release:

cg-update v1.2.0.9017

If an older updater rejects your Kilo version before it downloads this release,
first run cg-update v1.2.0.9017 from the global Compound GPID installation
directory, not from a linked consumer project. Then run the same command from
the consumer project to refresh and validate its local projection. Do not set
CG_INTERNAL_CALL, disable containment checks, downgrade Kilo, or change an
existing release tag to recover.

425 dated .cg-docs entries were older than the scan window and are not included in this release summary. One undated entry could not be assigned to the window. All three commits since the previous release were included.