@cassiomc1/forgeloop 2.0.0 → 2.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -7,7 +7,7 @@ alwaysApply: true
7
7
  This project is ForgeLoop-enabled. If your execution environment loaded this
8
8
  file, ForgeLoop applies regardless of model, provider, IDE, agent, or runtime.
9
9
  Do not treat ForgeLoop as vendor-specific, optional, or to follow only "in spirit".
10
- 1. Read [`LOOP_ENGINEERING.md`](../../LOOP_ENGINEERING.md) and [`PROTOCOL_INTEGRATION.md`](../../PROTOCOL_INTEGRATION.md).
10
+ 1. Read [`LOOP_ENGINEERING.md`](../../LOOP_ENGINEERING.md) from its Navigation section, loading each section before the phase it governs, and [`PROTOCOL_INTEGRATION.md`](../../PROTOCOL_INTEGRATION.md).
11
11
  2. Confirm [`PROJECT_PROFILE.md`](../../PROJECT_PROFILE.md) from real sources; initialize if in `template` mode.
12
12
  3. Use [`GUIDE_ROUTER.md`](../../GUIDE_ROUTER.md) to activate relevant guides and report IDs.
13
13
  3. For repository-wide textual discovery, prefer `forgeloop search` and treat its results as discovery only; do not use them as verification evidence or scope authority.
@@ -7,7 +7,7 @@ Do not treat ForgeLoop as vendor-specific, optional, or to follow only "in spiri
7
7
 
8
8
  Use these instructions across the repository while preserving local rules.
9
9
 
10
- - Read [`LOOP_ENGINEERING.md`](../LOOP_ENGINEERING.md) and [`PROTOCOL_INTEGRATION.md`](../PROTOCOL_INTEGRATION.md).
10
+ - Read [`LOOP_ENGINEERING.md`](../LOOP_ENGINEERING.md) from its Navigation section, loading each section before the phase it governs, and [`PROTOCOL_INTEGRATION.md`](../PROTOCOL_INTEGRATION.md).
11
11
  - If an official ForgeLoop structured integration is available in your host, prefer it for protocol operations; otherwise use the project-local ForgeLoop CLI. Never simulate ForgeLoop-managed lifecycle, claim, recovery, ledger, or completion state directly.
12
12
  - Confirm [`PROJECT_PROFILE.md`](../PROJECT_PROFILE.md) from evidence; initialize if in `template` mode.
13
13
  - Select context with [`GUIDE_ROUTER.md`](../GUIDE_ROUTER.md) and report activated guide IDs.
package/AGENTS.md CHANGED
@@ -6,7 +6,7 @@ file, ForgeLoop applies regardless of model, provider, IDE, agent, or runtime.
6
6
  Do not treat ForgeLoop as vendor-specific, optional, or to follow only "in spirit".
7
7
 
8
8
  1. Follow platform rules, the user's latest request, and local instructions first.
9
- 1. Read [`LOOP_ENGINEERING.md`](./LOOP_ENGINEERING.md) and [`PROTOCOL_INTEGRATION.md`](./PROTOCOL_INTEGRATION.md).
9
+ 1. Read [`LOOP_ENGINEERING.md`](./LOOP_ENGINEERING.md) from its Navigation section, loading each section before the phase it governs, and [`PROTOCOL_INTEGRATION.md`](./PROTOCOL_INTEGRATION.md).
10
10
  1. If an official ForgeLoop structured integration is available in your host, prefer it for protocol operations; otherwise use the project-local ForgeLoop CLI. Never simulate ForgeLoop-managed lifecycle, claim, recovery, ledger, or completion state directly.
11
11
  1. Inspect [`PROJECT_PROFILE.md`](./PROJECT_PROFILE.md). Confirm facts from sources; initialize if in `template` mode.
12
12
  1. Use [`GUIDE_ROUTER.md`](./GUIDE_ROUTER.md) to select relevant guides and report activated guide IDs.
package/CLAUDE.md CHANGED
@@ -8,7 +8,7 @@ Do not treat ForgeLoop as vendor-specific, optional, or to follow only "in spiri
8
8
  When working in this repository:
9
9
 
10
10
  1. Follow higher-level instructions, the user's latest request, and local rules first.
11
- 1. Read [`LOOP_ENGINEERING.md`](./LOOP_ENGINEERING.md) and [`PROTOCOL_INTEGRATION.md`](./PROTOCOL_INTEGRATION.md).
11
+ 1. Read [`LOOP_ENGINEERING.md`](./LOOP_ENGINEERING.md) from its Navigation section, loading each section before the phase it governs, and [`PROTOCOL_INTEGRATION.md`](./PROTOCOL_INTEGRATION.md).
12
12
  1. If an official ForgeLoop structured integration is available in your host, prefer it for protocol operations; otherwise use the project-local ForgeLoop CLI. Never simulate ForgeLoop-managed lifecycle, claim, recovery, ledger, or completion state directly.
13
13
  1. Verify [`PROJECT_PROFILE.md`](./PROJECT_PROFILE.md) against real sources; initialize if in `template` mode.
14
14
  1. Consult [`GUIDE_ROUTER.md`](./GUIDE_ROUTER.md), select relevant guides, and announce their IDs.
@@ -3,7 +3,7 @@ name: design-code-eng
3
3
  language: en
4
4
  description: "Visual direction, UX, motion, and perceived performance for premium digital experiences."
5
5
  version: "2026.09"
6
- last-reviewed: "2026-10-17"
6
+ last-reviewed: "2026-11-14"
7
7
  guide-id: design
8
8
  requires-gates:
9
9
  - design
@@ -29,7 +29,7 @@ Adopt this order as the default when creating a page from scratch; document an e
29
29
  5. **Reuse components and their interaction states**; adapt sample specifications to the product.
30
30
  6. **Add purposeful motion** only when it helps the experience, with reduced-motion and static fallbacks.
31
31
  7. **Run the Anti-Slop Checklist** before considering it ready.
32
- 8. **Audit and polish the affected experience** with the available project tools and direct browser/device inspection. Impeccable is an optional aid when installed and relevant; its availability is not a completion gate. Preserve the design system and recheck the changed states.
32
+ 8. **Audit and polish the affected experience** with the available project tools and direct browser/device inspection. When [Impeccable](https://impeccable.style/) is already available, its `audit` and `critique` commands can surface quality issues and `polish`/`harden` can address them in the changed scope; record the Impeccable version and the commands actually run. It is an optional aid: its availability or findings are not a completion gate, and it must not override the project's design system. Preserve the design system and recheck the changed states.
33
33
 
34
34
  Keep color and type decisions intentional. A familiar font, framework default, or repeated component is not a defect by itself; assess its fit, readability, hierarchy, and consistency in the actual interface.
35
35
 
@@ -324,6 +324,7 @@ appearance but cannot prove the state behavior or accessibility.
324
324
 
325
325
  **UI libraries and data visualization**
326
326
 
327
+ - Before adding JavaScript or a dependency for a UI behavior the platform may already provide (dialogs, popovers, tooltips via anchor positioning, view/entry-exit transitions, container queries, `field-sizing`, `:user-invalid` validation, scroll-driven effects), consult [Modern Web Guidance](https://developer.chrome.com/docs/modern-web-guidance) for the current native pattern and its fallback. Confirm each feature's Baseline status against the project's supported browser matrix, keep a lightweight fallback or progressive enhancement where support is incomplete, and preserve the design system and accessibility semantics. It is optional reference material: do not auto-install its CLI or skill, and treat its guidance as advice, not ForgeLoop evidence.
327
328
  - For accessible, composable, and customizable web components, consult [shadcn/ui](https://ui.shadcn.com/); adapt tokens, states, and composition to the project's visual system instead of copying defaults without intent.
328
329
  - For charts and data visualization, consult [TanStack Charts](https://github.com/TanStack/charts); preserve responsiveness, contrast, keyboard readability, and never rely on color alone to communicate series or states.
329
330
  - For subtle interaction sounds, consult [Cuelume](https://cuelume-site.pages.dev/); provide volume/mute controls and never rely on audio to communicate essential information.
@@ -594,7 +595,7 @@ For React-specific supplemental diagnostics after implementation, including desi
594
595
  - [ ] Where the platform exposes contrast/transparency preferences, including `prefers-contrast` or `forced-colors` when applicable, the opaque/less-transparent variant works; without a reliable media query, there is an equivalent in-product control.
595
596
  - [ ] No item from the "Blacklist" is present.
596
597
  - [ ] Tested at 320 CSS px reflow and desktop (1440px).
597
- - [ ] Reviewed the affected interface and states with available tools and browser/device evidence; optional Impeccable findings were addressed when that tool was used.
598
+ - [ ] Reviewed the affected interface and states with available tools and browser/device evidence; optional Impeccable findings (with the version and commands run) were addressed when that tool was used.
598
599
 
599
600
  ---
600
601
 
@@ -696,7 +697,7 @@ For React-specific supplemental diagnostics after implementation, including desi
696
697
 
697
698
  ## Sources and References (Base Skills)
698
699
 
699
- - TasteSkill / Anti-Slop: https://github.com/Leonxlnx/taste-skill | https://www.tasteskill.dev/
700
+ - Taste Skill (art direction and anti-slop review; MIT; adapted and version-pinned in the [Taste frontend guide](./taste-frontend-eng.md)): https://www.tasteskill.dev/ | https://github.com/Leonxlnx/taste-skill
700
701
  - Emil Kowalski (Design Engineering / Motion): https://github.com/emilkowalski/skills
701
702
  - GSAP: https://github.com/greensock/gsap-skills
702
703
  - ScrollWorld: https://github.com/oso95/scroll-world
@@ -706,6 +707,7 @@ For React-specific supplemental diagnostics after implementation, including desi
706
707
  - Apple Human Interface Guidelines (iOS/macOS): https://developer.apple.com/design/human-interface-guidelines/
707
708
  - Material Design 3 (Android): https://m3.material.io/
708
709
  - Microsoft Fluent Design / WinUI 3 (Windows): https://learn.microsoft.com/windows/apps/design/
710
+ - Modern Web Guidance (native web-platform patterns, fallbacks, and Baseline browser-compatibility guidance for coding agents; stewarded by the Chrome, Edge, Firefox, and MDN teams; Apache-2.0; referenced, not adapted; v1.0.0 current as of 2026-11-14): https://developer.chrome.com/docs/modern-web-guidance | https://github.com/GoogleChrome/modern-web-guidance
709
711
  - shadcn/ui (accessible, composable web components): https://ui.shadcn.com/
710
712
  - TanStack Charts (data visualization): https://github.com/TanStack/charts
711
713
  - Cuelume (web interaction sounds): https://cuelume-site.pages.dev/
@@ -716,7 +718,7 @@ For React-specific supplemental diagnostics after implementation, including desi
716
718
  - Pointer enhancement (only when `(hover: hover) and (pointer: fine)`; retain native controls/default cursor and equivalent tap interaction for touch/coarse pointers): https://cursify.ui-layouts.com/
717
719
  - Typography discovery (verify each font's author, license, weights, and hosting rights): https://uncut.wtf/
718
720
  - Creative coding and WebGL (semantic fallback, pause/offscreen behavior, performance budget, and asset/operator provenance): https://cables.gl/
719
- - Impeccable (interface auditing and polish): https://impeccable.style/
721
+ - Impeccable (design vocabulary and commands for building, auditing, refining, hardening, and documenting interfaces; Apache-2.0; referenced, not adapted; v4.9.1 current as of 2026-11-14): https://impeccable.style/ | https://github.com/pbakaus/impeccable | [command reference](https://impeccable.style/docs)
720
722
  - Gradient Studio (external procedural gradient exploration with CSS, Tailwind, and SCSS export by Amit Gajare; validate current provenance, reuse terms, output contrast, and performance budgets before adoption): https://gradientsaas.blogspot.com/
721
723
  - Liquid Glass Design (an independent inspiration gallery, not affiliated with Apple; not a specification or asset library): https://liquidglassdesign.com/
722
724
  - Guide to the material, glassmorphism, and web implementation: https://liquidglassdesign.com/what-is-liquid-glass
@@ -3,7 +3,7 @@ name: dotnet-aspnetcore-development-eng
3
3
  language: en
4
4
  description: "Specialist guide for architecture, implementation, testing, performance, security, data access, hosting, observability, and release of production .NET and ASP.NET Core applications."
5
5
  version: "2026.09"
6
- last-reviewed: "2026-10-13"
6
+ last-reviewed: "2026-11-14"
7
7
  guide-id: dotnet
8
8
  ---
9
9
 
@@ -75,9 +75,13 @@ Use structural project evidence for routing, but use source and configuration in
75
75
 
76
76
  ## 4. Version-sensitive decisions
77
77
 
78
- As of 2026-10-13, .NET 10 is the current LTS line; its latest patch is 10.0.12.
79
- .NET 9 is in maintenance and reaches end of support on 2026-11-10. These are
80
- dated references only: use the repository's pinned SDK and target framework.
78
+ .NET 10 is the current LTS line (supported until 2028-11-14; latest patch 10.0.15). .NET 8 and .NET 9
79
+ both reached end of support on 2026-11-10 and no longer receive security
80
+ updates; treat a repository still targeting them as carrying a supported-runtime
81
+ risk, and plan migration explicitly rather than as incidental cleanup. These are
82
+ dated references (reviewed 2026-11-14): use the repository's pinned SDK and
83
+ target framework, and check the official .NET support policy for the current
84
+ patch.
81
85
 
82
86
  Treat these as version-sensitive:
83
87
 
@@ -3,7 +3,7 @@ name: nodejs-backend-development-eng
3
3
  language: en
4
4
  description: "Specialist guidance for architecture, implementation, testing, security, performance, observability, and release of production Node.js backend services and workers."
5
5
  version: "2026.09"
6
- last-reviewed: "2026-10-13"
6
+ last-reviewed: "2026-11-14"
7
7
  guide-id: nodejs
8
8
  requires-gates:
9
9
  - threat-boundary
@@ -148,9 +148,12 @@ descendants; unrelated frontend packages remain isolated.
148
148
 
149
149
  ## 3. Runtime and module-system decisions
150
150
 
151
- As of 2026-10-13, Node.js 26 is Current and Node.js 24 is the latest LTS
152
- release. Production deployments should use an Active or Maintenance LTS line;
153
- check the official release schedule again when selecting a runtime.
151
+ As of 2026-11-14, Node.js 26 is Active LTS (promoted 2026-10-28) and Node.js 24
152
+ is Maintenance LTS. Node.js 26 is the last release on the twice-yearly
153
+ schedule; from Node.js 27 the project ships one major per year (April) and
154
+ promotes it to LTS each October. Production deployments should use an Active or
155
+ Maintenance LTS line; check the official release schedule again when selecting
156
+ a runtime.
154
157
 
155
158
  Record the actual runtime range before changing APIs:
156
159
 
@@ -3,7 +3,7 @@ name: sql-development-eng
3
3
  language: en
4
4
  description: "Specialist overlay guidance for SQL schemas, queries, migrations, and database-boundary changes."
5
5
  version: "2026.09"
6
- last-reviewed: "2026-10-13"
6
+ last-reviewed: "2026-11-14"
7
7
  guide-id: sql
8
8
  requires-gates:
9
9
  - threat-boundary
@@ -37,8 +37,9 @@ migration, reads credentials, or introspects a schema.
37
37
  The repository's database engine, version, migration policy, transaction model,
38
38
  compatibility window, and deployment process win over generic SQL advice. Use
39
39
  the matching engine's official reference first, then ISO/IEC 9075:2023 for
40
- portable semantics. The 2026-10-13 reference check covers PostgreSQL 18.6, MySQL 9.7 Innovation
41
- and 8.4 LTS, SQL Server 17 T-SQL, Oracle AI Database 26, and SQLite 3.54.0.
40
+ portable semantics. The 2026-11-14 reference check covers PostgreSQL 18.6, MySQL 9.7 LTS and
41
+ 8.4 LTS (Innovation releases now use calendar versions such as 26.7), SQL
42
+ Server 2025 (17.x) T-SQL, Oracle AI Database 26, and SQLite 3.54.0.
42
43
  These are reference points, not automatic upgrade targets.
43
44
 
44
45
  Never infer a dialect, isolation guarantee, identifier rule, timestamp
@@ -103,6 +104,6 @@ execution.
103
104
 
104
105
  - [SQLite SQL language](https://www.sqlite.org/lang.html)
105
106
  - [PostgreSQL documentation](https://www.postgresql.org/docs/)
106
- - [MySQL reference manuals](https://docs.oracle.com/cd/E17952_01/mysql-8.0-en/)
107
+ - [MySQL 9.7 reference manual](https://docs.oracle.com/cd/E17952_01/mysql-9.7-en/)
107
108
  - [Microsoft T-SQL reference](https://learn.microsoft.com/sql/t-sql/)
108
109
  - [Oracle Database SQL Language Reference](https://docs.oracle.com/en/database/oracle/oracle-database/)
@@ -3,7 +3,7 @@ name: taste-frontend-eng
3
3
  language: en
4
4
  description: "Contextual visual-taste review for premium frontend and brand-heavy work."
5
5
  version: "2026.09"
6
- last-reviewed: "2026-10-16"
6
+ last-reviewed: "2026-11-14"
7
7
  guide-id: taste
8
8
  ---
9
9
 
@@ -15,8 +15,9 @@ ForgeLoop router only when the work has that visual context. It is advisory: it
15
15
  does not create an approval gate, block an autonomous task, or require a
16
16
  specific framework, font, layout, animation library, or visual tool.
17
17
 
18
- The upstream inspiration is Taste Skill's design-read and anti-default
19
- approach. ForgeLoop keeps the useful review vocabulary while applying its own
18
+ The upstream inspiration is [Taste Skill](https://www.tasteskill.dev/)
19
+ ([source](https://github.com/Leonxlnx/taste-skill), MIT) and its design-read and
20
+ anti-default approach. ForgeLoop keeps the useful review vocabulary while applying its own
20
21
  protocol boundaries: user evidence, accessibility, performance, security, and
21
22
  the active product constraints have priority over aesthetic preference.
22
23
 
@@ -30,6 +31,15 @@ This identifies the upstream reference, not full feature parity or automatic
30
31
  synchronization. The guide's frontmatter version follows ForgeLoop's guide
31
32
  versioning separately.
32
33
 
34
+ As of 2026-11-14 the upstream repository is at
35
+ [v2.5.1](https://github.com/Leonxlnx/taste-skill/releases/tag/v2.5.1); that
36
+ release is not yet reviewed for this adaptation, so the guidance above still
37
+ reflects v2.0.0. When the optional upstream tools are used, use a copy whose
38
+ `design-taste-frontend` skill is 2.1.5 or later (see the
39
+ [upstream changelog](https://www.tasteskill.dev/changelog)): 2.1.5 escapes text
40
+ that `charts.js` and the split-heading fallback insert from user data, and
41
+ 2.1.4 stops one inspector run from deleting another run's browser profile.
42
+
33
43
  ForgeLoop adapts the content inventory, subject-specific concept, and screenshot
34
44
  correction practices. It deliberately keeps direction selection contextual
35
45
  rather than requiring a scripted draw. It does not adopt universal bans on
@@ -229,7 +239,9 @@ selected copy's requirements and output paths before use. Upstream tools may
229
239
  write project artifacts and user-level history outside ForgeLoop's evidence
230
240
  store; those files do not become attested evidence merely by existing.
231
241
 
232
- Prefer an available equivalent when it supports the same task checks. Treat
242
+ Prefer an available equivalent when it supports the same task checks; for
243
+ example, [Impeccable](https://impeccable.style/)'s `audit` and `critique`
244
+ commands cover a comparable interface review (see the Design guide). Treat
233
245
  upstream style findings as contextual recommendations, not new ForgeLoop gates.
234
246
  For external media, confirm the exact asset's license, attribution, and
235
247
  relevance; search results alone do not establish reuse rights. Identify found
@@ -242,7 +254,9 @@ evidence `NOT_VERIFIED` without claiming upstream tool coverage.
242
254
  For an existing interface, scan first and classify each issue as hierarchy,
243
255
  typography, color/contrast, composition, content, interaction, responsive
244
256
  behavior, accessibility, performance, or evidence. Fix the highest-leverage
245
- issues in small coherent batches. Re-read the whole system after each batch so
257
+ issues in small coherent batches. An optional interface auditor such as
258
+ Impeccable's `audit`/`critique` can seed this scan when it is already
259
+ available; its findings are recommendations, not ForgeLoop evidence. Re-read the whole system after each batch so
246
260
  local polish does not create a new inconsistency elsewhere.
247
261
 
248
262
  The final decision remains protocol-owned: this guide can recommend a visual
@@ -8,6 +8,27 @@ an execution environment appears in a compatibility list.
8
8
 
9
9
  <!-- FORGELOOP_PROJECT_PROTOCOL=REQUIRED -->
10
10
 
11
+ ## Navigation
12
+
13
+ - [Universal applicability](#universal-applicability)
14
+ - [Integration levels](#integration-levels)
15
+ - [Discovery surfaces](#discovery-surfaces)
16
+ - [Adaptive execution profiles and context presentation](#adaptive-execution-profiles-and-context-presentation)
17
+ - [Capability negotiation](#capability-negotiation)
18
+ - [CLI resolution policy](#cli-resolution-policy)
19
+ - [Protocol-owned state and no-simulation policy](#protocol-owned-state-and-no-simulation-policy)
20
+ - [Trusted command provenance](#trusted-command-provenance)
21
+ - [Missing tool capability](#missing-tool-capability)
22
+ - [Optional capability extensions](#optional-capability-extensions)
23
+ - [Delegation scope](#delegation-scope)
24
+ - [Instruction precedence](#instruction-precedence)
25
+ - [External workflow interaction](#external-workflow-interaction)
26
+ - [Harness and session continuity](#harness-and-session-continuity)
27
+ - [Structural quality integration](#structural-quality-integration)
28
+ - [Executable Policy Protocol Integration](#executable-policy-protocol-integration)
29
+ - [Structured integration surfaces](#structured-integration-surfaces)
30
+ - [Durable actions and authority boundary](#durable-actions-and-authority-boundary)
31
+
11
32
  ## Universal applicability
12
33
 
13
34
  If the active execution environment discovers a ForgeLoop project adapter,
package/README.md CHANGED
@@ -79,8 +79,8 @@ See the [23-guide maintenance map](./docs/GUIDE_MAINTENANCE.md) for review scope
79
79
  ## Distribution and license
80
80
 
81
81
  GitHub hosts source and issues. The core npm package is publicly available;
82
- the MCP companion retains restricted distribution. Stable `2.0.0` targets
83
- `latest`; publication requires verified release identity and native user audits.
82
+ the MCP companion retains restricted distribution. Stable `2.0.0` is published
83
+ on npm `latest`, with verified identity and native user audits.
84
84
  ForgeLoop-owned source and documentation are licensed under the
85
85
  [PolyForm Noncommercial License 1.0.0](./LICENSE). Commercial use is not granted
86
86
  by this license. Third-party notices are documented in
@@ -225,6 +225,7 @@ The contextual frontend taste guide is informed by Taste Skill:
225
225
 
226
226
  - Taste Skill, Copyright (c) 2026 Leonxlnx, MIT License.
227
227
  - Source: <https://github.com/leonxlnx/taste-skill>
228
+ - Project site: <https://www.tasteskill.dev/>
228
229
  - Reviewed baseline: [v2.0.0](https://github.com/Leonxlnx/taste-skill/tree/v2.0.0/skills/taste-skill),
229
230
  released 2026-10-13; adaptation reviewed 2026-10-16.
230
231
 
@@ -7,7 +7,7 @@
7
7
  ForgeLoop is a portable protocol and support CLI for verifiable engineering workflows. It records and validates task state, contracts, routing, checks, evidence, continuity, and optional code attestations. It does not become an agent scheduler, delegation service, source-control authority, or secret manager.
8
8
 
9
9
  Protocol version: 1
10
- Package version: 2.0.0
10
+ Package version: 2.1.0
11
11
 
12
12
  ## Canonical loop
13
13
 
@@ -50,7 +50,7 @@ uploading a repository through the browser.
50
50
 
51
51
  These are existing captures of the ForgeShop demo, taken from the production
52
52
  renderer at 1440 × 900 in the dark theme, aligned to Audit `0.3.0-rc.3` and
53
- ForgeLoop `2.0.0-rc.4`. The demo deliberately includes invalid, stale, blocked and
53
+ ForgeLoop `2.0.0`. The demo deliberately includes invalid, stale, blocked and
54
54
  unverified scenarios. Its warnings and coverage values do not establish
55
55
  completion or production readiness for your project.
56
56
 
@@ -227,7 +227,7 @@ Discover the deterministic task state path using `task-show`:
227
227
  forgeloop task-show --task task-contact-form-001 --json
228
228
  ```
229
229
 
230
- Then write the task contract to `.forgeloop/task-state/<taskKey>/contract.json`:
230
+ Write the contract to a project-relative input file outside `.forgeloop/task-state/` (for example `contract-input.json`). Writing it directly into the task-state directory creates legacy operational state next to canonical SQLite and makes later commands fail with `E_STORAGE_MIGRATION_REQUIRED`:
231
231
 
232
232
  ```json
233
233
  {
@@ -271,6 +271,13 @@ Then write the task contract to `.forgeloop/task-state/<taskKey>/contract.json`:
271
271
  }
272
272
  ```
273
273
 
274
+ Then let ForgeLoop record it transactionally (discovery first, when `next` asks for it):
275
+
276
+ ```bash
277
+ forgeloop discover --task task-contact-form-001 --json
278
+ forgeloop contract-create --task task-contact-form-001 --contract-file contract-input.json --json
279
+ ```
280
+
274
281
  ---
275
282
 
276
283
  ### Step 2 — Route Guides Deterministically
@@ -38,10 +38,9 @@ The published tarball includes the following consumer-facing groups:
38
38
 
39
39
  - **Runtime and protocol:** every maintained JavaScript module under `src/`,
40
40
  the guide registry, protocol templates, JSON schemas, completions, and the
41
- generic CI verifier. Four retired compatibility helpers remain in the
42
- repository for historical context and are explicitly excluded:
43
- `src/core/cli-metadata.js`, `src/core/decision-classification.js`,
44
- `src/core/gates.js`, and `src/core/workflow-compatibility.js`.
41
+ generic CI verifier. The four retired compatibility helpers that 2.0.0
42
+ excluded (`cli-metadata`, `decision-classification`, `gates`,
43
+ `workflow-compatibility`) were removed from `src/core` in 2.1.0.
45
44
  This includes the provider-neutral Repository Index runtime and its pinned
46
45
  `src/repository-index/tgrep-manifest.json`; native engine binaries are
47
46
  provisioned outside the npm tarball.
@@ -129,7 +128,7 @@ The tarball intentionally omits repository-only material:
129
128
 
130
129
  The package test checks all registered guide paths and these exclusion classes. It
131
130
  also enumerates `src/**/*.js` and fails if a maintained runtime module is
132
- missing from the candidate tarball or if a retired helper is reintroduced.
131
+ missing from the candidate tarball.
133
132
  The repository index remains a catalog: links from `DOCS_INDEX.md` to tests,
134
133
  historical plans, and source trees may intentionally resolve only in the full
135
134
  repository and are not package dependencies. The canonical documentation and
@@ -4,20 +4,44 @@ This is the current release checklist for the PolyForm Noncommercial-licensed
4
4
  `@cassiomc1/forgeloop` package. It is a preparation and verification checklist;
5
5
  it does not authorize publication.
6
6
 
7
- ## Stable 2.0.0 candidate — 2026-10-18
7
+ ## Stable 2.1.0 candidate — 2026-11-14
8
+
9
+ `2.1.0` is a minor release of the core package (the published error registry
10
+ gains every emitted code, 159 of them as `PUBLIC_UNCLASSIFIED`). Its runtime
11
+ changes are bound by
12
+ [`stable-2.1.0-writer-review.json.gz`](../benchmarks/storage-sqlite/stable-2.1.0-writer-review.json.gz),
13
+ a delta review against 2.0.0 with identical filesystem bindings and an explicit
14
+ disposition for every changed, added and removed module.
15
+ `scripts/check-release-channel.mjs` selects the review by exact package version
16
+ and never falls back to an earlier report.
17
+
18
+ Before dispatching `npm-publish.yml`: merge the release commit to `main`, tag it
19
+ `v2.1.0`, and dispatch from that tag with channel `latest` and confirmation
20
+ `PUBLISH PUBLIC PACKAGE`. Hosted parity, native Windows, rollback drills and
21
+ registry-user audits from 2.0.0 are not carried forward as evidence for these
22
+ bytes; the review records them as not repeated or post-publication. After
23
+ publication run:
8
24
 
9
- The core package version is `2.0.0`, targeting npm `latest`, with Node.js
25
+ ```bash
26
+ npm view @cassiomc1/forgeloop version dist-tags --json
27
+ npm run release:identity -- --version 2.1.0 --release-commit <release-tag-commit>
28
+ ```
29
+
30
+ ## Stable 2.0.0 publication — 2026-10-18
31
+
32
+ The published core package is `2.0.0` on npm `latest`, with Node.js
10
33
  24.19.0+ and built-in `node:sqlite`. The MCP companion retains restricted
11
34
  distribution and admits the stable core peer. Canonical SQLite is the sole
12
35
  supported operational writer; configuration, portable exports, immutable
13
36
  attachments and owner-bound maintenance evidence retain explicit file roles.
14
37
 
15
38
  The [release acceptance record](STABLE_2_ACCEPTANCE.md) identifies source-bound
16
- writer review, full verification, native user checks and recovery/exclusion
17
- receipts. A fresh hosted pair on the final release source and exact-head PR
18
- checks remain mandatory before publication. Do not bypass the release guard,
19
- reuse an earlier-source benchmark as final evidence, or infer publication from
20
- package metadata. Physical power-loss and production cutover are separate claims.
39
+ writer review, full verification, accepted final-source hosted parity, native
40
+ candidate and actual unversioned registry-user checks. Trusted publication and
41
+ release identity are verified. Its retained evidence separates the supported
42
+ writer boundary from physical power-loss, privileged external writers and
43
+ production cutover. Future releases require fresh exact-source checks; earlier
44
+ receipts are not evidence for changed runtime bytes.
21
45
 
22
46
  Verify the live registry and immutable release identity after publication:
23
47
 
@@ -134,10 +158,8 @@ never documentation, Git or task artifacts. Confirm the registry result
134
158
  before reporting success. The version remains an RC; promotion does not
135
159
  establish stable SQLite acceptance or production readiness.
136
160
 
137
- The older `promote-latest` operation in `npm-publish.yml` and
138
- `scripts/promote-rc-latest.mjs` is hard-bound to RC2. It is historical tooling,
139
- not an RC4 promotion path; do not dispatch `POINT LATEST TO RC2` for the
140
- current release. Its exact-identity and tag guards are retained.
161
+ The RC2-bound `promote-latest` operation and its promotion script were retired
162
+ after the stable 2.0.0 publication; `npm-publish.yml` now only publishes.
141
163
 
142
164
  ## ForgeLoop 2.0.0 candidate scope
143
165
 
@@ -249,8 +271,7 @@ deployment, and live data migration remain separate actions.
249
271
  other `src/config/guides.json` path; no repository-only guide state is
250
272
  packaged.
251
273
  - [ ] Every maintained `src/**/*.js` module is present in the candidate
252
- tarball; only the four explicitly retired compatibility helpers are
253
- excluded.
274
+ tarball; no runtime module is excluded.
254
275
 
255
276
  ## Protocol and attestation
256
277