@cassiomc1/forgeloop 2.0.0-rc.5 → 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.
Files changed (87) hide show
  1. package/.cursor/rules/project-loop.mdc +1 -1
  2. package/.github/copilot-instructions.md +1 -1
  3. package/AGENTS.md +1 -1
  4. package/CLAUDE.md +1 -1
  5. package/CONTRIBUTING.md +3 -1
  6. package/DOCS_INDEX.md +2 -0
  7. package/ENG/accessibility-eng.md +6 -6
  8. package/ENG/clean-code-eng.md +2 -2
  9. package/ENG/design-code-eng.md +17 -15
  10. package/ENG/documentation-quality-eng.md +10 -2
  11. package/ENG/dotnet-aspnetcore-development-eng.md +8 -4
  12. package/ENG/flutter-development-eng.md +38 -59
  13. package/ENG/games-code-design-web-eng.md +2 -2
  14. package/ENG/nodejs-backend-development-eng.md +7 -4
  15. package/ENG/perf-code-eng.md +3 -3
  16. package/ENG/php-development-eng.md +2 -2
  17. package/ENG/premium-sites-studio-eng.md +9 -2
  18. package/ENG/python-development-eng.md +7 -1
  19. package/ENG/rust-development-eng.md +22 -32
  20. package/ENG/sec-code-eng.md +19 -3
  21. package/ENG/sql-development-eng.md +5 -4
  22. package/ENG/taste-frontend-eng.md +125 -4
  23. package/ENG/test-code-eng.md +2 -2
  24. package/GUIDE_ROUTER.md +18 -4
  25. package/PROTOCOL_INTEGRATION.md +21 -0
  26. package/README.md +15 -13
  27. package/THIRD_PARTY_NOTICES.md +60 -6
  28. package/docs/AGENT_PROTOCOL_SUMMARY.md +1 -1
  29. package/docs/AGENT_SKILL.md +16 -0
  30. package/docs/DOCUMENTATION_GUIDE.md +6 -0
  31. package/docs/FORGELOOP_AUDIT.md +1 -1
  32. package/docs/GETTING_STARTED.md +8 -1
  33. package/docs/GUIDE_MAINTENANCE.md +106 -0
  34. package/docs/PACKAGE_CONTENTS.md +22 -5
  35. package/docs/RELEASE_CHECKLIST.md +68 -35
  36. package/docs/REVENUE_CENTRIC_DESIGN.md +69 -0
  37. package/docs/SECURITY_AUDIT_SKILL.md +131 -0
  38. package/docs/SECURITY_REVIEW.md +6 -0
  39. package/docs/STABLE_2_ACCEPTANCE.md +127 -0
  40. package/docs/TROUBLESHOOTING.md +171 -0
  41. package/docs/documentation-manifest.json +244 -0
  42. package/package.json +12 -7
  43. package/scripts/generate-forgeloop-skill.mjs +8 -0
  44. package/scripts/verify-revenue-design-skill.mjs +37 -0
  45. package/scripts/verify-security-audit-skill.mjs +68 -0
  46. package/skills/forgeloop/SKILL.md +8 -0
  47. package/skills/forgeloop/references/revenue-centric-design/LICENSE +30 -0
  48. package/skills/forgeloop/references/revenue-centric-design/PIN.json +14 -0
  49. package/skills/forgeloop/references/revenue-centric-design/SKILL.md +64 -0
  50. package/skills/forgeloop/references/revenue-centric-design/references/playbook.md +36 -0
  51. package/skills/security-audit/AI-AND-LLM.md +83 -0
  52. package/skills/security-audit/ATTACK-CLASSES.md +130 -0
  53. package/skills/security-audit/CLIENT-SIDE.md +83 -0
  54. package/skills/security-audit/CLOUD-AND-DEPLOYMENT.md +86 -0
  55. package/skills/security-audit/DATA-ISOLATION-AND-LIFECYCLE.md +84 -0
  56. package/skills/security-audit/DESKTOP-MOBILE-AND-LOCAL-IPC.md +89 -0
  57. package/skills/security-audit/HUNTING.md +251 -0
  58. package/skills/security-audit/LICENSE +21 -0
  59. package/skills/security-audit/MEMORY-SAFETY-AND-BINARY.md +101 -0
  60. package/skills/security-audit/PIN.json +30 -0
  61. package/skills/security-audit/PROTOCOLS-RPC-AND-MESSAGING.md +81 -0
  62. package/skills/security-audit/RECONNAISSANCE.md +156 -0
  63. package/skills/security-audit/RESOURCE-EXHAUSTION-AND-AVAILABILITY.md +78 -0
  64. package/skills/security-audit/SKILL.md +192 -0
  65. package/skills/security-audit/SUPPLY-CHAIN-AND-RELEASE.md +73 -0
  66. package/skills/security-audit/VALIDATION-AND-REPORTING.md +186 -0
  67. package/skills/security-audit/WEB-PROTOCOL-AND-AUTH.md +105 -0
  68. package/skills/security-audit/report-schema.json +461 -0
  69. package/skills/security-audit/validate-coverage-ledger.cjs +872 -0
  70. package/skills/security-audit/validate-coverage-ledger.test.cjs +740 -0
  71. package/skills/security-audit/validate-findings.cjs +773 -0
  72. package/skills/security-audit/validate-findings.test.cjs +652 -0
  73. package/src/core/completion-artifacts.js +4 -7
  74. package/src/core/diagnosis.js +3 -5
  75. package/src/core/diagnostic-record.js +4 -4
  76. package/src/core/error-codes.js +180 -2
  77. package/src/core/next-action-recovery-phases.js +3 -0
  78. package/src/core/next-action-review-correction.js +26 -0
  79. package/src/core/next-action-review-phase.js +25 -15
  80. package/src/core/parsers/dotnet-project.js +221 -0
  81. package/src/core/parsers/limits.js +9 -0
  82. package/src/core/parsers/pubspec.js +307 -0
  83. package/src/core/parsers/shared.js +4 -0
  84. package/src/core/project-detection.js +6 -527
  85. package/src/core/reconcile-closure.js +5 -0
  86. package/src/core/review-correction.js +51 -0
  87. package/src/storage/capabilities.js +1 -1
@@ -0,0 +1,106 @@
1
+ # Engineering guide maintenance
2
+
3
+ ForgeLoop's [guide registry](../src/config/guides.json) contains 23 guides.
4
+ The [router](../GUIDE_ROUTER.md) selects relevant context; a catalog entry is
5
+ not evidence that its toolchain is installed, its examples were executed, or
6
+ its target application is ready for release.
7
+
8
+ ## Review scope and authority
9
+
10
+ The catalog consistency review dated 2026-10-17 covered every registered guide
11
+ for activation claims, precedence, optional-tool boundaries, verification
12
+ language, version handling, and related documentation. Local source and
13
+ validators govern routing, metadata, packaging, and evidence. Official
14
+ version-matched sources govern language/platform semantics. This review is
15
+ not a new certification of every API, release, framework, device, or external
16
+ link, and it does not execute consumer applications.
17
+
18
+ Use this precedence when maintaining guidance:
19
+
20
+ 1. Preserve platform rules, the user's request, repository constraints, and
21
+ the canonical ForgeLoop protocol.
22
+ 2. Derive activation from `src/core/project-detection.js`, its specialist
23
+ parsers, `src/core/router.js`, and the public project-evidence schemas.
24
+ 3. Read guide gates and completion requirements from registered frontmatter;
25
+ prose examples do not create extra lifecycle gates or protocol enums.
26
+ 4. Preserve project versions and architecture. Dated release examples are
27
+ reference material, not permission to upgrade a compiler or framework.
28
+ 5. Treat named tools and aesthetic defaults as contextual choices. Do not
29
+ install a missing optional tool or introduce a user-approval gate for a
30
+ reversible local choice. Reuse scoped authority already given.
31
+ 6. Keep unavailable checks and observations separate from passing evidence,
32
+ legal compliance, publication, deployment, and production readiness.
33
+
34
+ ## Catalog maintenance map
35
+
36
+ The focus column records the boundary inspected and retained, or the
37
+ substantive correction made. All rows remain subject to the review limits
38
+ above; retained guidance does not imply a fresh external release audit.
39
+
40
+ | ID | Guide | Maintenance focus |
41
+ | --- | --- | --- |
42
+ | `premium` | [Premium websites](../ENG/premium-sites-studio-eng.md) | Clarified production stages versus runtime gates and genuine client/publication authority |
43
+ | `clean` | [Clean code](../ENG/clean-code-eng.md) | Retained cohesion, public contracts, cancellation, observability, and risk-based dependency guidance; clarified existing installation authority |
44
+ | `test` | [Testing](../ENG/test-code-eng.md) | Retained proportional tests, protected checks, unavailable-tool reporting, and observed evidence; clarified existing installation authority |
45
+ | `security` | [Security](../ENG/sec-code-eng.md) | Retained threat-boundary gate, negative tests, and advisory Cloudflare companion boundary; clarified existing installation authority |
46
+ | `design` | [Design](../ENG/design-code-eng.md) | Preserved product tokens, made example styling and Impeccable contextual, and removed install-capable verifier examples |
47
+ | `taste` | [Taste frontend](../ENG/taste-frontend-eng.md) | Retained contextual v2 adaptation, source/asset provenance, no aesthetic authority, and screenshot-based review |
48
+ | `performance` | [Performance](../ENG/perf-code-eng.md) | Clarified async I/O versus CPU offloading; retained measured baselines, field/lab separation, and bounded resources |
49
+ | `accessibility` | [Accessibility](../ENG/accessibility-eng.md) | Defaulted missing profile to AA without an artificial approval gate; corrected contrast and native-control keyboard guidance |
50
+ | `games` | [Web games](../ENG/games-code-design-web-eng.md) | Retained bounded fixed-step simulation, authoritative resync, validated procedural generation, capability fallback, and deployment checks; clarified installation authority |
51
+ | `documentation` | [Documentation](../ENG/documentation-quality-eng.md) | Added guide-specific checks for factual activation, gates, defaults, optional tools, and release claims |
52
+ | `flutter` | [Flutter](../ENG/flutter-development-eng.md) | Replaced prospective routing instructions with implemented manifest detection and task-specific verification semantics |
53
+ | `dotnet` | [.NET](../ENG/dotnet-aspnetcore-development-eng.md) | Retained structural SDK project detection, scoped ASP.NET/ABP overlays, version compatibility, and build/release distinctions |
54
+ | `nodejs` | [Node.js](../ENG/nodejs-backend-development-eng.md) | Retained bounded backend evidence, module/runtime compatibility, cancellation, resource controls, and operational verification |
55
+ | `rust` | [Rust](../ENG/rust-development-eng.md) | Grounded the release review in primary Rust sources and narrowed safety/API claims; retained Cargo/MSRV and ownership boundaries |
56
+ | `c` | [C](../ENG/c-development-eng.md) | Retained bounded native build/source identity, pointer/ABI contracts, cleanup, sanitizers, and missing-tool limits |
57
+ | `cpp` | [C++](../ENG/cpp-development-eng.md) | Retained native identity, RAII/lifetime/ABI policy, bounded concurrency, and exact-standard verification |
58
+ | `java` | [Java](../ENG/java-development-eng.md) | Retained static Maven/Gradle/Bazel evidence, scoped topology, runtime/build separation, and bounded executor policy |
59
+ | `sql` | [SQL](../ENG/sql-development-eng.md) | Retained host-project overlay, dialect/version discovery, transaction/retry policy, and separate migration authority |
60
+ | `go` | [Go](../ENG/go-development-eng.md) | Retained bounded module/workspace topology, language/toolchain distinction, goroutine ownership, and race/fuzz evidence limits |
61
+ | `typescript` | [TypeScript](../ENG/typescript-development-eng.md) | Retained JSONC/config ownership, runtime-neutral identity, erased-type/runtime validation distinction, and compiler API migration boundary |
62
+ | `php` | [PHP](../ENG/php-development-eng.md) | Aligned the source fallback description with both `<?php` and `<?=` recognized by the parser |
63
+ | `swift` | [Swift](../ENG/swift-development-eng.md) | Retained SwiftPM/native target composition, source-backed identity, concurrency/FFI policy, and signing/platform evidence limits |
64
+ | `python` | [Python](../ENG/python-development-eng.md) | Explicitly documented reference-only status: automatic structural Python routing is not implemented |
65
+
66
+ ## Revalidation procedure
67
+
68
+ For a guide change, inspect the registered path, frontmatter, related router
69
+ rules, representative valid/invalid fixtures, and affected consumer docs.
70
+ Check an external version-sensitive claim against the project's pinned
71
+ version and the relevant official source before revising it. Update
72
+ `last-reviewed` when that guide is materially revalidated; do not change dates
73
+ on untouched guides merely to make the catalog look fresh.
74
+
75
+ For policy changes, compare related guides as well: a safe default in one
76
+ document must not become a mandatory tool, approval, rewrite, or installation
77
+ in another. Preserve explicit user requirements and real blocking decisions.
78
+
79
+ Run proportional checks, including the existing documentation suite:
80
+
81
+ ```bash
82
+ npm run docs:check
83
+ python3 scripts/validate_markdown.py
84
+ npm run pack:check
85
+ npm run security-skill:check
86
+ ```
87
+
88
+ Use `npm run verify:fast` while editing and `npm run verify:prepush` before a
89
+ PR. Those commands verify repository consistency and applicable code/package
90
+ behavior; they do not run all 23 consumer toolchains. New documentation must
91
+ be registered in the documentation manifest and review matrix. Add
92
+ consumer-facing pages to the package allowlist, and derive generated content
93
+ through its existing generator.
94
+
95
+ ## Primary reference points for changed guidance
96
+
97
+ - [WCAG contrast](https://www.w3.org/WAI/WCAG22/Understanding/contrast-minimum.html)
98
+ and [ARIA Authoring Practices](https://www.w3.org/WAI/ARIA/apg/).
99
+ - [Node.js event-loop guidance](https://nodejs.org/en/learn/asynchronous-work/dont-block-the-event-loop).
100
+ - [Official Rust 1.99.0 announcement](https://blog.rust-lang.org/2026/10/01/Rust-1.99.0/).
101
+ - ForgeLoop's [project detector](../src/core/project-detection.js),
102
+ [PHP recognizer](../src/core/php-project.js),
103
+ [guide registry](../src/config/guides.json), and
104
+ [project-evidence schema](../schemas/routing-input.schema.json).
105
+ - [Repository dependency policy](https://github.com/cassiomc1/forgeloop/blob/main/scripts/check-dependency-policy.mjs) and
106
+ [package metadata](../package.json) for runtime dependencies and versions.
@@ -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.
@@ -56,6 +55,9 @@ The published tarball includes the following consumer-facing groups:
56
55
  ASP.NET Core and ABP are conditional routing overlays on the `dotnet` guide,
57
56
  not additional package guides. The package does not install or invoke
58
57
  framework, compiler, build, package-manager, or database tooling.
58
+ `docs/GUIDE_MAINTENANCE.md` ships the full catalog maintenance map and
59
+ revalidation boundaries; it does not add automatic Python routing or new
60
+ lifecycle gates.
59
61
  - **Initialization material:** the root protocol and integration documents,
60
62
  the PolyForm Noncommercial license, third-party notices, the target profile template, and every path listed by
61
63
  `src/core/templates.js`. These files are read by `init` and `update`, so
@@ -76,6 +78,12 @@ The published tarball includes the following consumer-facing groups:
76
78
  documentation are also packaged.
77
79
  The generated portable ForgeLoop Agent Skill and `docs/AGENT_SKILL.md` are
78
80
  packaged as instruction/documentation content, not runtime authority.
81
+ The optional Cloudflare companion at `skills/security-audit/` also ships,
82
+ including its upstream references, schema, validators and tests, MIT
83
+ license, and `PIN.json`. Its usage guide at `docs/SECURITY_AUDIT_SKILL.md`
84
+ and offline `scripts/verify-security-audit-skill.mjs` checker are packaged.
85
+ It adds no runtime dependency or automatic scan and is not copied by
86
+ `init`/`update` into host skill directories.
79
87
  Provider implementation modules ship under `src/`, but packaged source file
80
88
  does not mean a supported public import path; the generic `./providers`
81
89
  subpath remains unexported.
@@ -120,7 +128,7 @@ The tarball intentionally omits repository-only material:
120
128
 
121
129
  The package test checks all registered guide paths and these exclusion classes. It
122
130
  also enumerates `src/**/*.js` and fails if a maintained runtime module is
123
- missing from the candidate tarball or if a retired helper is reintroduced.
131
+ missing from the candidate tarball.
124
132
  The repository index remains a catalog: links from `DOCS_INDEX.md` to tests,
125
133
  historical plans, and source trees may intentionally resolve only in the full
126
134
  repository and are not package dependencies. The canonical documentation and
@@ -146,3 +154,12 @@ gate before `npm publish --provenance --access public`.
146
154
  Publication therefore remains owned by the authorized manual GitHub Actions
147
155
  workflow and uses public npm access for the core package; local package inspection proves the
148
156
  candidate boundary but does not publish it.
157
+
158
+ ## Optional product design companion
159
+
160
+ The generated ForgeLoop skill includes the maintained
161
+ `skills/forgeloop/references/revenue-centric-design/` reference tree. It ships
162
+ a focused skill, local journey playbook, complete custom source-available
163
+ license and integrity pin. `docs/REVENUE_CENTRIC_DESIGN.md` and
164
+ `scripts/verify-revenue-design-skill.mjs` describe and verify it. Upstream media
165
+ and updater scripts are excluded; external theme references are pinned links.
@@ -4,14 +4,54 @@ 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
- ## Current published candidate — 2026-10-14
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 public core package is `2.0.0-rc.4`; npm `latest` and `next` both resolve
10
- to RC4. It requires Node.js 24.19.0+ with built-in `node:sqlite`. The MCP
11
- companion retains restricted distribution. RC4 is a release candidate;
12
- `soleSQLiteWriter` remains false and stable/production acceptance is open.
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
33
+ 24.19.0+ and built-in `node:sqlite`. The MCP companion retains restricted
34
+ distribution and admits the stable core peer. Canonical SQLite is the sole
35
+ supported operational writer; configuration, portable exports, immutable
36
+ attachments and owner-bound maintenance evidence retain explicit file roles.
37
+
38
+ The [release acceptance record](STABLE_2_ACCEPTANCE.md) identifies source-bound
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.
45
+
46
+ Verify the live registry and immutable release identity after publication:
47
+
48
+ ```bash
49
+ npm view @cassiomc1/forgeloop version dist-tags --json
50
+ npm view @cassiomc1/forgeloop@2.0.0 gitHead dist.integrity --json
51
+ npm run release:identity -- --version 2.0.0 --release-commit <release-tag-commit>
52
+ ```
13
53
 
14
- Observed release evidence:
54
+ ## Historical RC4 release evidence
15
55
 
16
56
  - [RC4 verification and publication](https://github.com/cassiomc1/forgeloop/actions/runs/38629809865)
17
57
  passed full release checks and published with provenance.
@@ -20,20 +60,11 @@ Observed release evidence:
20
60
  - [Default latest-install audit](https://github.com/cassiomc1/forgeloop/actions/runs/38669237414)
21
61
  installed the unversioned public package with a fresh npm cache,
22
62
  configuration, install prefix and project; all 15 checks passed on each OS.
23
- This run uses the test-harness branch `codex/latest-user-audit-20261014`;
24
- its `latest` input is not present in the main-branch workflow.
63
+ Those results describe RC4, not a later stable package.
25
64
 
26
- The published npm `gitHead` and immutable `v2.0.0-rc.4` tag identify
65
+ The published RC4 npm `gitHead` and immutable `v2.0.0-rc.4` tag identify
27
66
  `d05c17cddda6a09581d526732b08eb0789b9734f`. The RC3 tag is retained; its
28
- publication was cancelled before npm publication. RC4 carries those runtime
29
- fixes plus the Windows archive-repair test correction.
30
-
31
- Verify the live registry before relying on a channel:
32
-
33
- ```bash
34
- npm view @cassiomc1/forgeloop version dist-tags --json
35
- npm view @cassiomc1/forgeloop@2.0.0-rc.4 gitHead dist.integrity --json
36
- ```
67
+ publication was cancelled before npm publication.
37
68
 
38
69
  ## Runtime corrections after RC2
39
70
 
@@ -44,12 +75,18 @@ acceptance remains separate; a passing new-user audit does not change
44
75
  `soleSQLiteWriter` or authorize a stable 2.x release. Candidates publish to
45
76
  `next` under the existing release-channel policy.
46
77
 
47
- The `Published npm new-user SQLite audit` workflow supports `candidate` and
48
- `npm` package sources. Before a PR, test the packed candidate in an isolated
78
+ The `Published npm new-user SQLite audit` workflow supports `candidate`, `npm` and
79
+ `latest` package sources. Before a PR, test the packed candidate in an isolated
49
80
  installation, home directory and project on each platform. After publication,
50
- dispatch the same workflow with source `npm` and the exact new version. Require
51
- every check to pass, including live Jev health, concurrent task creation,
52
- SQLite integrity and a completed-task backup restored to a fresh directory.
81
+ dispatch the same workflow with source `latest` and the exact expected new version.
82
+ The `latest` mode installs the unversioned package with fresh home, cache, npm
83
+ configuration, install prefix and project directories. It retains registry
84
+ metadata alongside the observed audit report. Use `npm` for a separate exact-version
85
+ control. Require
86
+ every check to pass, including both bundled companion integrity checks, live
87
+ Jev health, concurrent task creation,
88
+ SQLite integrity, current-cycle review diagnosis/correction, and a completed-task
89
+ backup restored to a fresh directory.
53
90
  Supply `FORGELOOP_NPM_AUDIT_JEV_KEY` through GitHub Actions secrets and remove
54
91
  temporary credentials after the runs finish.
55
92
 
@@ -89,8 +126,8 @@ p95 result is claimed by the short path. The existing 1,000-task parity run
89
126
  `38483369676` is retained for review; no fresh 200-repeat benchmark is dispatched.
90
127
 
91
128
  The writer inventory covers every current `src` JavaScript module and records
92
- imports plus potential write sites. Alias, computed-path, external-caller, and
93
- transitive-authority review remain incomplete. The inventory explicitly keeps
129
+ imports plus potential write sites. At that historical RC checkpoint, alias, computed-path, external-caller, and
130
+ transitive-authority review remained incomplete. The inventory explicitly keeps
94
131
  `wholeConsumerClosure: false`; it prevents drift and does not authorize setting
95
132
  `soleSQLiteWriter` to true.
96
133
 
@@ -121,17 +158,14 @@ never documentation, Git or task artifacts. Confirm the registry result
121
158
  before reporting success. The version remains an RC; promotion does not
122
159
  establish stable SQLite acceptance or production readiness.
123
160
 
124
- The older `promote-latest` operation in `npm-publish.yml` and
125
- `scripts/promote-rc-latest.mjs` is hard-bound to RC2. It is historical tooling,
126
- not an RC4 promotion path; do not dispatch `POINT LATEST TO RC2` for the
127
- 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.
128
163
 
129
164
  ## ForgeLoop 2.0.0 candidate scope
130
165
 
131
- A stable 2.0.0 release is not ready while SQLite migration plan §10 has
132
- open consumer-closure, current-source performance, or platform evidence. Keep
133
- all acceptance boxes open until their evidence is bound to the exact candidate
134
- revision.
166
+ A stable 2.0.0 publication requires the source-bound acceptance record and final
167
+ release-source checks. The preparation checklist below is not itself a pass;
168
+ retain exact evidence for each applicable requirement.
135
169
 
136
170
  The 2.0.0 candidate carries the SQLite storage transition alongside the
137
171
  existing protocol, routing, provider, documentation, and package surfaces. The
@@ -237,8 +271,7 @@ deployment, and live data migration remain separate actions.
237
271
  other `src/config/guides.json` path; no repository-only guide state is
238
272
  packaged.
239
273
  - [ ] Every maintained `src/**/*.js` module is present in the candidate
240
- tarball; only the four explicitly retired compatibility helpers are
241
- excluded.
274
+ tarball; no runtime module is excluded.
242
275
 
243
276
  ## Protocol and attestation
244
277
 
@@ -0,0 +1,69 @@
1
+ # Revenue-centric design companion
2
+
3
+ ForgeLoop includes an optional [revenue-centric design companion](../skills/forgeloop/references/revenue-centric-design/SKILL.md)
4
+ for product journeys, activation, pricing clarity and retention. It adapts
5
+ [heliocosta-dev/revenue-centric-design at the reviewed commit](https://github.com/heliocosta-dev/revenue-centric-design/tree/1942760c2242f609bf63ce2c97204f5a1791bd68),
6
+ a curation of Richard ([@richardrx](https://x.com/richardrx)).
7
+
8
+ ## Availability and scope
9
+
10
+ The source and npm package include the focused skill, an offline journey
11
+ playbook, full upstream license and pin manifest under
12
+ `skills/forgeloop/references/revenue-centric-design/`. The original twelve
13
+ theme references are linked at an immutable upstream commit; media, updater
14
+ scripts, scraping dependencies and API configuration are excluded.
15
+
16
+ Ask an agent to read the companion at that package or source path for relevant
17
+ product work. It is not activated for ordinary protocol or storage maintenance.
18
+ Hosts requiring skill discovery can copy that complete directory into their
19
+ project skill directory after inspecting any existing destination. Preserve
20
+ its license, attribution and pin. `init`, `update` and the skill generator do
21
+ not install or synchronize this discovery copy.
22
+
23
+ ```bash
24
+ node scripts/verify-revenue-design-skill.mjs
25
+ # From a consumer project with a local ForgeLoop installation:
26
+ node node_modules/@cassiomc1/forgeloop/scripts/verify-revenue-design-skill.mjs
27
+ ```
28
+
29
+ The checker verifies the explicit file set and SHA-256 hashes with CRLF
30
+ normalized to LF for portable text checkouts. The pin detects drift against a
31
+ reviewed manifest; it is not a signature, sandbox or evidence of business impact.
32
+ For a copied directory, call the exported `verifyRevenueDesignSkill` function
33
+ with its absolute `rootDir`.
34
+
35
+ ## Use with ForgeLoop
36
+
37
+ Inspect the actual user journey, identify observed friction and propose a
38
+ small reversible change. Pair a user-value metric with a guardrail such as
39
+ successful cancellation, accessibility, error recovery or price comprehension.
40
+ Treat principles, anecdotes and claimed statistics as hypotheses requiring
41
+ context and original-source verification. Browser checks establish behavior;
42
+ conversion and retention claims require appropriate real measurement.
43
+
44
+ For ForgeLoopAudit, relevant work concerns read-only project selection, a first
45
+ successful inspection, understandable evidence, useful errors and navigation.
46
+ This addition does not add commercial flows, tracking or paid experiments to
47
+ the auditor. Audit remains read-only and keeps its own verification commands.
48
+
49
+ The canonical contract, guide router, runtime, gates and validators retain
50
+ all authority. This companion adds no guide ID, runtime dependency, provider,
51
+ automatic gate or completion requirement. Its advice cannot establish
52
+ `COMPLETE` or `VALID`. Preserve informed choice: honest proof and pricing,
53
+ visible renewal terms, reversible defaults and usable cancellation/opt-out.
54
+
55
+ ## Attribution and usage terms
56
+
57
+ The [complete upstream license](../skills/forgeloop/references/revenue-centric-design/LICENSE)
58
+ is retained unchanged. It requires attribution to Richard and the source,
59
+ preservation of its full terms in copies/derivatives, and excludes gambling,
60
+ betting, casino and real-money games-of-chance uses, including loot boxes.
61
+ These are source-available custom terms, not an OSI-approved open-source
62
+ license or ForgeLoop's PolyForm license. Copy the license with any adaptation.
63
+
64
+ The adaptation replaces the broad upstream entrypoint with a focused workflow
65
+ and local journey matrix. It links source themes progressively, keeps external
66
+ research unverified until checked, and preserves ForgeLoop authority and user
67
+ choice. To update it, review the upstream commit and terms, update the
68
+ adaptation and pin together, then verify integrity, documentation and package
69
+ contents. Do not run the upstream updater as part of a ForgeLoop release.
@@ -0,0 +1,131 @@
1
+ # Cloudflare security audit companion
2
+
3
+ ForgeLoop bundles Cloudflare's optional
4
+ [`security-audit`](../skills/security-audit/SKILL.md) skill for source-based
5
+ security questions, focused vulnerability reviews, and explicitly requested
6
+ codebase audits. It provides a repeatable investigation workflow alongside
7
+ the canonical [security guide](../ENG/sec-code-eng.md).
8
+
9
+ The companion is instruction content with local report validators. It adds no
10
+ runtime dependency, scanner service, automatic scan, or ForgeLoop completion
11
+ gate. ForgeLoopAudit inspects protocol evidence; this companion investigates
12
+ source-level security boundaries. These are separate capabilities.
13
+
14
+ ## Availability and setup
15
+
16
+ The complete skill directory ships in the source repository and core npm
17
+ package at `skills/security-audit/`. It includes the domain references,
18
+ findings schema, both validators, their tests, the upstream MIT license, and
19
+ ForgeLoop's pin manifest. The upstream files are unchanged.
20
+
21
+ From a ForgeLoop checkout, verify the copy before using it:
22
+
23
+ ```bash
24
+ node scripts/verify-security-audit-skill.mjs
25
+ ```
26
+
27
+ In a project with a local npm installation, use:
28
+
29
+ ```bash
30
+ node node_modules/@cassiomc1/forgeloop/scripts/verify-security-audit-skill.mjs
31
+ ```
32
+
33
+ Ask an agent to read the companion's `SKILL.md` at that package or checkout
34
+ path and use its guidance for the requested scope. Hosts that require skill
35
+ discovery can instead copy the **entire** `skills/security-audit/` directory
36
+ into their supported project skill directory, such as
37
+ `.agents/skills/security-audit/`. Inspect an existing destination first;
38
+ preserve local modifications rather than overwriting them. Keep all companion
39
+ files together, including `LICENSE` and `PIN.json`. Verify a copied directory
40
+ with `verifySecurityAuditSkill({ rootDir: absoluteSkillDirectory })`, exported
41
+ by the same checker module.
42
+
43
+ ForgeLoop `init` and `update` do not install or synchronize this skill into a
44
+ host's discovery directories. Updating ForgeLoop also does not update a copied
45
+ host skill. No global installation or external Skills CLI is required.
46
+
47
+ ## Choose the appropriate mode
48
+
49
+ | Request | Mode and result |
50
+ | --- | --- |
51
+ | Explain a security control or investigate one suspected issue | Guidance mode; read relevant references, without automatically creating audit files or running all phases |
52
+ | Audit a codebase, perform a comprehensive security review, or produce audit reports | Full audit mode; follow all six upstream phases, including independent verification and coverage accounting |
53
+ | Fix a confirmed issue | A separately scoped ForgeLoop implementation contract with regression checks; the audit itself does not modify target source |
54
+
55
+ Example agent request for a focused review:
56
+
57
+ > Read the bundled security-audit skill. Review the authorization boundary in
58
+ > src/auth in guidance mode. Return source-grounded observations and exact
59
+ > unresolved facts.
60
+
61
+ Example agent request for a full audit:
62
+
63
+ > Read the bundled security-audit skill. Audit this repository, follow all six
64
+ > phases, and report partial coverage and unavailable capabilities explicitly.
65
+
66
+ For a full audit, select scope, source revision, profile, and an external
67
+ output directory under the upstream rules. Use an in-target output directory
68
+ only when the user explicitly chooses it and version control ignores the
69
+ entire directory. Respect host write permissions. Audit artifacts belong to
70
+ the audit output directory, outside ForgeLoop-owned task state.
71
+
72
+ Full audit mode requires independent delegated hunters and verifiers. A
73
+ single agent's self-review cannot satisfy that independence. Target-controlled
74
+ execution additionally requires the upstream OS-enforced sandbox: network
75
+ isolation, sanitized environment, read-only target/toolchain, assigned scratch
76
+ writes, and explicit resource limits. A generic terminal sandbox or a
77
+ `run-check` receipt does not establish all these controls. If a required
78
+ capability is unavailable, retain the exact blocker and incomplete or
79
+ `needs_validation` status as required upstream; do not weaken the evidence
80
+ bar. No live endpoint probing, dependency fetching, publication, or paid
81
+ service use is authorized by loading this skill.
82
+
83
+ ## Findings and ForgeLoop authority
84
+
85
+ Preserve upstream verdicts:
86
+
87
+ - `confirmed`: a source-grounded boundary failure with the required validation;
88
+ severity describes the demonstrated impact.
89
+ - `needs_validation`: an exact source-grounded hypothesis with a missing fact;
90
+ it has no severity.
91
+ - `rejected`: a candidate disproved by validation.
92
+
93
+ The six phases produce architecture and coverage records, findings, independent
94
+ record verification, and reports. Run both upstream validators against the
95
+ artifacts using the argument contracts documented in the skill. They validate
96
+ report structure and consistency; passing them does not prove that the target
97
+ is secure, that every attack surface was covered, or that a finding is true.
98
+
99
+ Findings remain advisory observations. They cannot satisfy ForgeLoop gates,
100
+ change claims, advance phases, or establish `COMPLETE` or `VALID`. The
101
+ [Security Review provider](./SECURITY_REVIEW.md) is a separate host-injected
102
+ observation API; this bundle does not register a provider or import reports
103
+ into it. Its normalized finding contract is not interchangeable with the
104
+ upstream report schema.
105
+
106
+ When a finding requires a fix, inspect it, bind it to a scoped contract, and
107
+ verify the behavior through canonical ForgeLoop checks. Use `run-check` for
108
+ exact-command provenance where execution is authorized. Never copy a report
109
+ directly into task state or relabel it as ForgeLoop-owned evidence. The
110
+ canonical runtime and validators retain all completion authority.
111
+
112
+ ## Provenance and maintenance
113
+
114
+ - Source: [cloudflare/security-audit-skill](https://github.com/cloudflare/security-audit-skill).
115
+ - Pinned commit: `c1c8a8c1471069fb0e188eeaff69b8e8db6564a8`.
116
+ - Upstream directory: `skills/security-audit/`; `LICENSE` comes from the
117
+ upstream repository root.
118
+ - License: [MIT, copyright Cloudflare, Inc.](../skills/security-audit/LICENSE),
119
+ retained separately from ForgeLoop's license.
120
+ - [PIN.json](../skills/security-audit/PIN.json) records SHA-256 hashes of every
121
+ upstream file, including the license. The checker rejects changed, missing,
122
+ extra, or symlinked entries without executing the skill.
123
+ The repository's `.gitattributes` preserves the entire companion tree as
124
+ bytes, including CJS validators and the license, across CRLF checkout settings.
125
+
126
+ The hashes detect drift against the reviewed manifest; they are not a
127
+ signature or a sandbox. Updating the companion is an explicit maintenance
128
+ change: review the exact upstream revision and license, replace the complete
129
+ upstream tree, regenerate its file hashes, update the documented pin, run the
130
+ integrity checker and both upstream validator suites, and verify package
131
+ contents. Do not silently fetch a newer revision during normal operation.
@@ -57,6 +57,12 @@ ForgeLoop-owned validation and evidence contract.
57
57
 
58
58
  ## Operational rules
59
59
 
60
+ The optional bundled [Cloudflare security audit companion](./SECURITY_AUDIT_SKILL.md)
61
+ is an agent workflow with a separate report schema. It does not register a
62
+ Security Review provider or automatically import its findings. An upstream
63
+ `needs_validation` record must not be promoted to a severity-bearing confirmed
64
+ finding or canonical evidence by an adapter.
65
+
60
66
  - Keep registration lazy and explicit.
61
67
  - Use a host-owned provider and a bounded request.
62
68
  - Treat findings as advisory observations, not proof of `VALID`, `COMPLETE`,