F-Layer v1.2.1 — Usable guides and reviewed translations

Digest

F-Layer v1.2.1 makes the documentation easier to use: start with a practical
Quick Start, read clearer product descriptions, and follow verified Russian
and Chinese guides without translation-draft notices. Release publication now
requires a completed, closed milestone. Runtime and CLI behavior remain compatible
with 1.1.0 and the preliminary 1.2.0 snapshot.

What's Changed

Added

• Quick Start with installation, offline checks, help and first-deployment links
  in English, Russian and Simplified Chinese.
• The F-Layer company slide in the README and documentation landing pages,
  with a compact header logo and square favicon.
• Accountable AIna review of all 18 authored RU/ZH-CN pages, bound to the exact
  English source and translated text. Missing API translations remain English.

Changed

• Describe the supported Yandex Cloud, secure SSH gateway and diagnostic workflows
  in language engineers and prospective customers can understand.
• Require a completed native release milestone before stable publication; use
  F-Layer vX.Y.Z titles and preserve published tags.
• Keep translation-review evidence in metadata rather than a notice on every
  approved page. AI reviews are identified explicitly and never called human approvals.

Fixed

• Clipped landing-page slides and oversized header branding.
• Russian ownership wording, Chinese virtual-machine terminology, localized
  documentation links and consistent v1.2.1 installation examples.
• Translation drift checks now invalidate AI approval when the translated text
  changes, even if the English source stays unchanged.

Validation

• Python quality passed on the exact released master commit.
• Documentation quality gates passed on the exact released master commit.
• Release artifact validation passed on the exact released master commit.
• Multilingual Pages deployment passed on this exact source. All 18 authored Russian/Chinese translations passed accountable AI review; missing references retain English fallback.
• release-1.2 is completed and closed with zero open items; Task #27 and Feature #8 acceptance receipts are recorded before stable publication.
• Tagged artifact audit passed annotated-tag/version ownership, repeated byte-identical builds, source-archive rebuild parity, archive ownership and wheel RECORD checks.
• The attached wheel, source archive and build-evidence.json were downloaded and matched their audited SHA256 values and sizes before publication.
• Tests use isolated resources; no live cloud mutation or PyPI upload was performed.

Source commit: d61cf94.

Breaking Changes

None for runtime APIs or CLI commands. Documentation review metadata now supports
explicitly authorized AI reviewers; human-only review remains the default.

Try it from source

git clone https://github.com/Fuzzy-Technologies/F-Layer.git
cd F-Layer
git checkout v1.2.1
python -m pip install .
flayer --help
python -m flayer check --format json

Python 3.11 or newer is required. Package-index publication is a separate operation.

Notes

• This patch finalizes the release-1.2 documentation/security scope on the
  released baseline; later runtime work remains in develop.
• The v1.2.0 preliminary tag and audited assets remain unchanged for traceability.
• No live cloud deployment or PyPI upload is performed by this release.
• Detailed changelog
• Release milestone

F-Layer v1.2.0 — Documentation and security preview

Digest

Preliminary publication: release-1.2 is not complete. This snapshot was
published as stable before milestone acceptance was complete. The stable
classification was withdrawn on 2026-10-08. Task #27 and Feature #8 still require
genuine human translation reviews; stable publication requires the completed,
closed milestone. The existing tag and audited assets are preserved for traceability.

F-Layer v1.2.0 makes its documentation easier to inspect and publish: every tracked
file has an accountable place in the generated reference, and EN/RU/ZH-CN routes
show their actual translation status. The documentation toolchain includes the
setuptools security correction. Runtime and CLI behavior stay compatible with
1.1.0; Russian and Simplified Chinese prose remains explicitly draft.

What's Changed

Added

• File and definition inventories that distinguish public installed-wheel APIs,
  rendered repository Markdown, locale overlays, and source-only engineering files.
• Complete canonical Markdown navigation, including policy, ADR templates,
  architecture, development, release guidance, and the GitHub PR template.
• Executable CLI and callable-protocol API coverage, whole-package wheel/source
  parity, exact anchors, local-link checks, and rendered-page reachability gates.
• Implemented architecture diagrams and strict multilingual builds with localized
  navigation, draft/fallback banners, and 18 source-bound RU/ZH-CN draft pages.
• A review handoff linking canonical sources, both locale drafts, required human
  roles, current source hashes, and publication evidence requirements.

Fixed

• Broken generated links from repository review material to locale draft sources,
  with regression evidence for both languages and preserved fragments.
• Snapshot installation instructions select v1.2.0 in English, Russian,
  and Simplified Chinese and retain the supported console/module commands.

Changed

• New files in existing coverage categories are discovered automatically;
  unknown or ambiguous categories and missing wheel payloads fail validation.
• Reviewed translation status remains separate from build success. Drafts and
  missing translations are labeled explicitly; automation creates no approvals.

Security

• Pin setuptools 83.0.0 in the documentation toolchain for
  GHSA-h35f-9h28-mq5c / CVE-2026-59890, replacing vulnerable 80.9.0.
• Preserve all other documentation pins, the Hatchling package backend,
  static API rendering, and existing ownership/mutation-consent boundaries.

Validation

• Python quality passed on the exact released master commit.
• Documentation quality gates passed on the exact released master commit.
• Release artifact validation passed on the exact released master commit.
• Tagged artifact audit passed annotated-tag/version ownership, repeated byte-identical builds, source-archive rebuild parity, archive ownership and wheel RECORD checks.
• The attached wheel, source archive and build-evidence.json were downloaded and matched their audited SHA256 values and sizes before publication.
• Tests use isolated resources; no live cloud mutation or PyPI upload was performed.

Source commit: 3937447.

Breaking Changes

None. Runtime APIs, CLI commands, owned-state contracts, and provider behavior
remain compatible with 1.1.0. This release adds documentation and validation tooling.

Try it from source

git clone https://github.com/Fuzzy-Technologies/F-Layer.git
cd F-Layer
git checkout v1.2.0
python -m pip install .
flayer --help
python -m flayer check --format json

Python 3.11 or newer is required. The attached wheel is an alternative to source
installation; a package-index upload is a separate owner-controlled operation.

Notes

• Selects accepted release-1.2 PRs #46, #48, #59, and #60 on the tagged 1.1.0
  baseline, plus bounded release stabilization. Plugin discovery, ecosystem
  integration contracts, and the static-site deployment profile remain later work.
• All 18 authored RU/ZH-CN pages remain drafts. Generated APIs and untranslated
  repository material use explicit English fallback. Human editorial/technical
  reviews remain outstanding, so Task #27, Feature #8, and the milestone must
  be completed before a stable release can be published.
• No live cloud deployment or PyPI upload is performed by this release.
• Detailed changelog
• Release provenance

F-Layer v1.1.0 — Installable package and user guide

Digest

F-Layer 1.1.0 makes the infrastructure baseline easier to install and operate:
a typed Python package, an installed flayer command, and practical guides for
configuration, diagnostics, and the first owned gateway deployment. Release
artifacts now have repeatable build and ownership checks. This is an additive
release; its validation uses isolated resources and does not establish live
cloud readiness.

What's Changed

Added

• A PEP 561 typed distribution and flayer console command, with one canonical
  source for runtime, wheel, and source-archive versions.
• Repeated byte-identical wheel/source-archive builds, source-archive wheel rebuild
  parity, archive ownership checks, metadata/RECORD verification, and build evidence.
• CI previews of audited distributions and a separately guarded, owner-confirmed
  manual PyPI workflow. PyPI upload is not enabled or performed by this release.
• User guides for installation, provider configuration, CLI results, and the
  first gateway deployment with explicit ownership and mutation consent.

Changed

• Adopt the FuzzyRoutines-style FL logo family and clearer documentation navigation.
• Align Markdown table columns for readable source and validate their formatting.
• Present exact stable-tag installation instructions, released console behavior,
  and the detailed changelog in both source archives and generated documentation.

Security

• Include only owned tracked rebuild inputs and reject substituted archive payloads,
  recognizable credential material, unsafe paths, and unexpected root files.
• Keep PyPI publication opt-in and separate from GitHub Releases; preserve 1.0.0's
  explicit resource ownership and bounded cloud mutation contracts.

Validation

• Python quality passed on the exact released master commit.
• Documentation quality gates passed on the exact released master commit.
• Release artifact validation passed on the exact released master commit.
• Annotated tag, package/source versions, repeated byte-identical builds, source-archive rebuild parity, owned archive members, credential-pattern checks, and wheel RECORD hashes passed.
• The wheel, source archive, and build-evidence.json are attached. Downloaded release assets matched their audited SHA256 values and sizes before publication.
• Tests use isolated fakes; no live cloud validation or PyPI upload was performed.

Source commit: c977cc48978854141ef22b955693b3b6a0560bbf. Tagged artifact audit.

Breaking Changes

None. Version 1.1.0 adds packaging, documentation, and release checks to the 1.0.0
runtime contracts; existing python -m flayer commands remain supported.

Try it from source

git clone https://github.com/Fuzzy-Technologies/F-Layer.git
cd F-Layer
git checkout v1.1.0
python -m pip install .
flayer --help
python -m flayer check --format json

Python 3.11 or newer is required. See the shipped user guide for an isolated
virtual environment and explicitly scoped cloud configuration.

Notes

• Adds accepted release-1.1 PRs #39, #40, and #41 to the tagged 1.0.0 baseline.
  Complete repository documentation coverage, draft RU/ZH pages, ecosystem
  contracts, plugins, and the static-site profile remain in later milestone work.
• Live cloud deployment, guest SSH/tunnel readiness, human translation approval,
  and actual PyPI publication are not claimed by these offline release checks.
• Install from the exact tag or attached wheel; a package-index upload is separate.
• Detailed changelog
• Release provenance

F-Layer v1.0.0 — Owned infrastructure baseline

Digest

F-Layer 1.0.0 is the first versioned infrastructure baseline: manage explicitly
owned Yandex Cloud stacks, prepare a secure SSH gateway, and inspect health through
bounded diagnostics. Configuration, recovery, and cleanup have deterministic
offline test evidence; live cloud deployment and guest readiness still require
operator validation.

What's Changed

Added

• Strict configuration and durable state tied to explicit stack ownership.
• Yandex Cloud inventory and six-resource create/status/destroy orchestration,
  including idempotency, recovery, rollback, and ownership-checked cleanup.
• A secure SSH gateway profile with explicit access rules and verified generated
  artifacts; no private key or personal infrastructure material is distributed.
• Status/check commands and opt-in, resource-bounded HTTP health/benchmark probes.
• English installed-wheel API documentation and safe master-only Pages publishing;
  Russian and Simplified Chinese clearly indicate unavailable translations.
• Offline CI, linked-Task completion, branch cleanup, and ADR 0014 documenting
  scoped release history and the Fuzzy Technologies changelog format.

Validation

• Python quality passed on the exact released master commit.
• Documentation quality gates passed on the exact released master commit.
• Annotated tag, package/source versions, repeated byte-identical builds, source-archive rebuild parity, owned archive members, credential-pattern checks, and wheel RECORD hashes passed.
• The wheel, source archive, and build-evidence.json are attached. Downloaded release assets matched their audited SHA256 values and sizes before publication.
• Tests use isolated fakes; no live cloud validation or PyPI upload was performed.

Source commit: 0c7cfc0434c69b02ad5a0720595080a965f598a1. Tagged artifact audit.

Breaking Changes

None relative to a previous stable F-Layer release; this is the initial versioned
baseline. Ownership/state contracts apply from the first release.

Try it from source

git clone https://github.com/Fuzzy-Technologies/F-Layer.git
cd F-Layer
git checkout v1.0.0
python -m pip install .
python -m flayer --help
python -m flayer check --format json

Python 3.11 or newer is required. Cloud mutations additionally need an explicitly
selected account, owned plan/state paths, and mutation consent; check the shipped
architecture guides before operating a real stack.

Notes

• Includes accepted release-1.0 PRs #32, #34, #35, #36, #37, #38, #42, and #43.
  Packaging/console distribution refinements and the user guide belong to 1.1;
  complete repository documentation coverage, reviewed locales, plugins,
  ecosystem contracts, and the additional static-site profile are later work.
• Cloud RUNNING does not establish guest SSH/tunnel readiness. Guest image and
  external service behavior must be validated in the operator's environment.
• PyPI upload is not performed. Install from the exact tag or attached wheel.
• Detailed changelog
• Release provenance