Every release, verifiable before you trust it

• The PowerShell self-test no longer depends on the console code page: each child process is run with its streams redirected to files read back as UTF-8, so one tree gives one verdict under code page 437 and under UTF-8.
• A project can declare the build outputs its records cite in a project-owned file, `.ai/context/link-policy.json`. Such a reference is reported as unverified while the file is absent and checked like any other once the build has produced it; an undeclared path or a missing source file still fails.
• Additive for adopters: a project that declares nothing sees exactly what it saw before.

Upgrade notes for v1.20.1 Release notes and tag forgeos-1.20.1.tar.gz forgeos-1.20.1.tar.gz.sha256

• Task closure resolves its target and related plan to a real path and refuses anything outside the task and plan directories. Writes are staged, so a failure leaves the records as they were, and two different records sharing one name are reported as a conflict and left untouched.
• `forgeos brief` measures what it is about to print and drops optional content whole, in a fixed order, naming what it dropped. Mandatory content is never truncated; when it alone overflows the budget the brief says so. Sizes are an estimate — UTF-8 bytes divided by four — and are labelled that way.
• One mandatory-rule contract across both shells: tab-indented rules and case-insensitive conditions now behave the same on PowerShell and POSIX. The self-test grew from 241 to 246 cases per shell.
• Compatibility: a waiver written in the older free-text form is rejected at closure and must be rewritten with scope, reason, risk, and a resolving reference.

Release notes and tag forgeos-1.20.0.tar.gz forgeos-1.20.0.tar.gz.sha256

• A read-only intake report names what kind of project a repository is — governing documents, discovery required, codebase reconstruction, website, or enterprise system — each with a confidence rating and the evidence paths it used.
• A readiness forecast rates product truth, architecture, data, governance, and implementation, every one a status with a short reason beside the map coverage it found.
• The report names which prompt family the next session belongs to, and the one file to read first. It is built from names, sizes, and presence, and never opens a governing document.
• The install-matrix validation jobs now skip with a notice in an adopted project instead of failing on release tooling that deliberately never ships to adopters.

Release notes and tag forgeos-1.19.0.tar.gz forgeos-1.19.0.tar.gz.sha256

• A project's own documents become compact, cited maps that are read first, so no specification is paid for twice.
• Two modes decided by what the repository holds: governing documents build seven maps under `.ai/product/`; a project without them prepares six discovery records instead.
• Thirteen templates ship for the two modes, with a workflow defining the procedure — classify without opening files, rank sources, index each one once, and cite it by a stable identifier.
• A new informational validation row reports the mode and map coverage. It checks presence only, never opens a document, and never fails a build.

Release notes and tag forgeos-1.18.0.tar.gz forgeos-1.18.0.tar.gz.sha256

• A whole-session protocol bounds a long working session end to end — single agent, read by section, validate once per change, stop in the usage-risk zone. It relaxes no validation, review, or gate.
• `forgeos brief`: a compact session launcher held to a strict size budget and measured by the command itself.
• Session policy is provider-neutral, and effort is raised per decision rather than per session.
• When the next capability is blocked, the brief names the blocker and any task already waiting, and invents nothing.

Release notes and tag forgeos-1.17.0.tar.gz forgeos-1.17.0.tar.gz.sha256

• Compact validation output is now the default, with verbose detail available when a reviewer asks for it.
• Generated session packages now default to single-agent, bounded-context work unless the owner explicitly authorizes a broader review.
• The discovery workflow no longer delegates architecture work automatically; deep reads stay behind explicit routing.
• Adopter templates keep their own project guidance intact during updates.
• The self-test suite now respects web projects that legitimately own a root package manifest, and validates 210 cases per shell.

Release notes and tag forgeos-1.16.0.tar.gz forgeos-1.16.0.tar.gz.sha256

• `forgeos prompt`: one package answering which session to start, what to read first, the scope, the prohibitions, and the shape the final report must take.
• The package is built from the project's own files. When a source it needs is missing, it names the source and its remedy instead of printing a prompt built on guesses.
• The push, tag, and deploy lines can only ever say refused or ask-the-owner.
• Governance is reflected, never granted: the command opens no window and authorizes nothing.

Release notes and tag forgeos-1.15.31.tar.gz forgeos-1.15.31.tar.gz.sha256

• The first release published from the public repository. Everything this site states about ForgeOS is checkable against this tag.
• Ships as a checksummed archive built from the tag — a sync source, not a product bundle. It carries the portable half of the blueprint and the scaffolding a new project needs, and deliberately not the repository's own answers or history.
• Archives are byte-identical across Windows and POSIX, so the published checksum is reproducible rather than merely recorded.
• Every gating validation check passes on Windows PowerShell 5.1 and on POSIX bash.
• MIT licence.

Release notes and tag forgeos-1.15.30.tar.gz forgeos-1.15.30.tar.gz.sha256