@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,127 @@
1
+ # Stable ForgeLoop 2.0.0 acceptance
2
+
3
+ ForgeLoop **2.0.0** is published on npm **latest**. The immutable `v2.0.0` tag
4
+ and registry `gitHead` identify `4ff11bb4bc4be39b095a151a323f1388dad0d819`.
5
+ [PR #229](https://github.com/cassiomc1/forgeloop/pull/229) merged after all six
6
+ required checks passed on that head. The protected merge has the same release
7
+ tree and retains the reviewed commit as an ancestor.
8
+
9
+ ## Published identity and native user checks
10
+
11
+ The [trusted publication](https://github.com/cassiomc1/forgeloop/actions/runs/39133661722)
12
+ passed full verification and published with GitHub OIDC and signed provenance.
13
+ `release:identity` independently verified the version, remote tag, `gitHead`,
14
+ SHA-1 and SHA-512 of the actual registry tarball. npm processing completed
15
+ before user tests began. The archive SHA-256 is
16
+ `326fbd81db54b9164f862a383fba4861817bd31ee325cf07252fb0b1101bc835`.
17
+
18
+ The [fresh latest-install matrix](https://github.com/cassiomc1/forgeloop/actions/runs/39135810569)
19
+ installed the **unversioned** package with separate fresh home, npm cache,
20
+ configuration, prefix and project directories. Each host resolved **2.0.0**,
21
+ with matching registry identity and all sixteen checks passing:
22
+
23
+ | Native host | Runtime | Result |
24
+ | --- | --- | --- |
25
+ | macOS ARM64 | Node 24.19.0 | 16/16 PASS |
26
+ | Windows x64 | Node 24.19.0 | 16/16 PASS |
27
+ | Linux x64 | Node 24.19.0 | 16/16 PASS |
28
+
29
+ Checks cover both bundled companions, live Jev health, initialization and
30
+ persistence, claim conflicts, contract/routing/preflight, eight concurrent
31
+ writers, WAL/SQLite/foreign-key integrity, tamper detection, mixed-state
32
+ refusal, backup/no-overwrite, a real review finding and correction with fresh
33
+ verification, validator-backed completion and completed-task restore into a new
34
+ directory. The temporary GitHub TypeSafe secret was removed after all reports
35
+ were retained and verified. Raw registry/user receipts are retained as
36
+ `benchmarks/storage-sqlite/stable-2.0.0-latest-*.json.gz`.
37
+
38
+ ## Supported operational writer boundary
39
+
40
+ The [source review at the release tag](https://github.com/cassiomc1/forgeloop/blob/v2.0.0/benchmarks/storage-sqlite/stable-2.0.0-writer-review.json.gz)
41
+ binds all 511 core/MCP runtime JavaScript modules, 105 literal filesystem
42
+ modules, 457 lexical filesystem/wrapper references and sixteen indirect
43
+ references. Ninety-five filesystem modules retain reviewed bytes; ten deltas
44
+ have explicit dispositions. No nonliteral runtime import is present in that
45
+ inventory. Source hashes and the collector are retained with the review.
46
+
47
+ Supported CLI, Integration API and MCP dispatch select canonical SQLite.
48
+ Operational state, events, receipts, claims and indexed domain records share
49
+ the native transaction boundary. Portable writers reject operational namespaces;
50
+ mixed layouts, foreign or expired contexts and actor-supplied persistence
51
+ capabilities fail closed. Explicit migration/restore retain ownership and
52
+ quiescence admission. The package advertises `soleSQLiteWriter: true` for this
53
+ supported boundary.
54
+
55
+ Configuration, installation manifests, portable exports/bundles and backups,
56
+ immutable attachments, owner-bound maintenance journals/archives, repository
57
+ index/cache, transport state and private scratch files remain explicit file
58
+ roles. They are not writable operational mirrors. Legacy data requires explicit
59
+ migration; native projects do not silently fall back to JSON.
60
+
61
+ `scripts/verify-stable-storage-review.mjs` checks complete runtime-module
62
+ membership and normalized source SHA-256 hashes. The stable channel guard
63
+ requires that source check. New modules or changed runtime bytes require review.
64
+ The manifest is not a signature, universal absence proof or substitute for
65
+ behavioral verification. The older call-name inventory retains
66
+ `wholeConsumerClosure: false` and remains discovery-only.
67
+
68
+ ## Source-bound release validation
69
+
70
+ Full local pre-push on `780b9338` passed 3,109 tests with zero failures and sixteen
71
+ optional skips, plus coverage, critical coverage, lint, dependency/complexity,
72
+ documentation, package, MCP and Python validators. The final delta at `4ff11bb4`
73
+ corrected only three Markdown formatting errors; exact-head required CI and
74
+ full tag-publication verification passed on that final source. The
75
+ [native candidate matrix](https://github.com/cassiomc1/forgeloop/actions/runs/39128718653)
76
+ also passed 16/16 on each host before publication. All post-merge workflows,
77
+ including full Windows, Node compatibility, package, documentation and CodeQL,
78
+ passed on the identical protected-merge tree.
79
+
80
+ The [final-source hosted pair](https://github.com/cassiomc1/forgeloop/actions/runs/39128716481)
81
+ meets the owner-approved plan §9 criterion: 1,000 canonical-rich-all tasks,
82
+ ordinary ten events, one selected task with 1,000 events, 200 timed/resource
83
+ samples per side, exact output parity, validated closed workers and parent,
84
+ matching before/after source manifests, and successful root cleanup observers.
85
+
86
+ | Operation | Native p95 | Pinned baseline p95 |
87
+ | --- | --- | --- |
88
+ | taskListTool | 2,161.862 ms | 4,361.678 ms |
89
+ | projectTasksResource | 2,141.102 ms | 4,364.023 ms |
90
+
91
+ Both native p95 values are lower than baseline
92
+ `ee9ce11123d4e728d3dbc92f5d62d4bf41bb79c5`. This proves the recorded replacement
93
+ criterion, not every original benchmark dimension. The raw receipt deliberately
94
+ retains `releaseThresholdsVerified: false`; it has not been relabeled as full
95
+ original-matrix acceptance. Final-source artifacts are retained under
96
+ `benchmarks/storage-sqlite/stable-2.0.0-hosted-*`.
97
+
98
+ [Linux and Windows public rollback](https://github.com/cassiomc1/forgeloop/actions/runs/39126195649)
99
+ passed all sixteen cases per host at `61447313`; macOS passed the same sixteen
100
+ cases at that revision with unchanged source. The
101
+ [Linux/Windows old-client exclusion drill](https://github.com/cassiomc1/forgeloop/actions/runs/39125628347)
102
+ passed at `e9139a55`; the macOS drill passed at `61447313` with cleanup. These
103
+ receipts retain their precise source revisions and inventoried installation
104
+ boundary. Later stable metadata and documentation changes do not expand those
105
+ exclusion claims. Current-source full tests and fresh registry checks remain
106
+ separate evidence.
107
+
108
+ ## ForgeLoopAudit alignment
109
+
110
+ [ForgeLoopAudit](https://github.com/cassiomc1/forgeloop/tree/main/ForgeLoopAudit) pins the actual public 2.0.0 archive
111
+ and release commit. All 52 shipped schema files were compared with the exact
112
+ release source before regenerating its trusted 31-schema provenance. Its own
113
+ lineage checks and recaptured README images identify stable core 2.0.0. Audit
114
+ retains its separate full verification, native-platform and browser gates; core
115
+ publication does not publish an Audit binary. Audit remains a read-only unsigned
116
+ preview and uses the public Integration API.
117
+
118
+ ## Limits
119
+
120
+ Process-kill drills do not establish physical power-loss behavior. Privileged
121
+ raw SQLite access, arbitrary host providers/external commands and uninventoried
122
+ legacy installations are outside this proof. Production migration still needs a
123
+ named target, backup, writer inventory and operator-enforced quiescence. No live
124
+ user project was migrated by these release tests. Historical migration
125
+ scoreboards retain their original source/date and do not describe current
126
+ release completion. No production deployment or Audit binary publication is
127
+ implied.