@reservamos/browser-analytics 1.1.6 → 1.1.7-alpha.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.
package/CHANGELOG.md CHANGED
@@ -1,5 +1,13 @@
1
1
  # Change Log
2
2
 
3
+ ## Unreleased
4
+
5
+ - Align npm and Yarn lockfiles with Fingerprint Pro SPA 1.3.3 and its compatible JavaScript agent.
6
+ - Avoid identifying with a Fingerprint client before its agent finishes loading.
7
+ - Add a reproducible Compound Engineering workflow shared by Codex, Claude Code, and Cursor.
8
+ - Add canonical fast and full validation commands used locally and in CI.
9
+ - Verify generated package entrypoints and align the package's type declaration paths with the generated declaration bundle.
10
+
3
11
  ## 1.1.6
4
12
 
5
13
  - Use taxonomy-consistent Title Case properties for `Purchase Confirmation Viewed`, including `Operation Id` instead of `order_number`.
package/README.md CHANGED
@@ -79,9 +79,20 @@ analytics.track.purchaseConfirmation({
79
79
  });
80
80
  ```
81
81
 
82
- ## Development workflow (OpenSpec)
82
+ ## Development workflow
83
83
 
84
- This repo uses [OpenSpec](https://github.com/Fission-AI/OpenSpec) for spec-driven development. Changes are planned as artifacts under `openspec/changes/` before implementation.
84
+ This repository uses Compound Engineering for the agent-assisted lifecycle and [OpenSpec](https://github.com/Fission-AI/OpenSpec) as the persistent planning format for large or high-risk changes. Small, bounded fixes do not require duplicate OpenSpec and `ce-plan` artifacts.
85
+
86
+ The authoritative local checks are:
87
+
88
+ ```bash
89
+ ./validate.sh # format, lint, typecheck, and tests
90
+ ./validate.sh --full # plus build and package-entrypoint verification
91
+ ```
92
+
93
+ Run the full command before a push or pull request. See [the workflow](docs/agents/compound-engineering-workflow.md), [environment setup](docs/agents/setup-and-environments.md), and [review criteria](CODING_STANDARDS.md).
94
+
95
+ ### OpenSpec prerequisites
85
96
 
86
97
  ### Prerequisites
87
98
 
@@ -92,22 +103,24 @@ npm install -g @fission-ai/openspec
92
103
  openspec --version # must be >= 1.4.1
93
104
  ```
94
105
 
95
- ### Commands
106
+ ### OpenSpec commands
96
107
 
97
108
  Use these slash commands in Cursor or Claude Code:
98
109
 
99
- | Command | Purpose |
100
- |---|---|
110
+ | Command | Purpose |
111
+ | --------------- | -------------------------------------------------------- |
101
112
  | `/opsx-explore` | Explore ideas and clarify requirements (no code changes) |
102
- | `/opsx-propose` | Create a change with proposal, design, specs, and tasks |
103
- | `/opsx-apply` | Implement tasks from an active change |
104
- | `/opsx-sync` | Sync delta specs from a change to main specs |
105
- | `/opsx-archive` | Archive a completed change |
113
+ | `/opsx-propose` | Create a change with proposal, design, specs, and tasks |
114
+ | `/opsx-apply` | Implement tasks from an active change |
115
+ | `/opsx-sync` | Sync delta specs from a change to main specs |
116
+ | `/opsx-archive` | Archive a completed change |
106
117
 
107
- ### Typical flow
118
+ ### Full-lane flow
108
119
 
109
120
  1. `/opsx-explore` — think through the problem
110
121
  2. `/opsx-propose my-change-name` — generate planning artifacts
111
122
  3. `/opsx-apply` — implement the tasks
112
123
  4. `/opsx-sync` — merge specs into `openspec/specs/`
113
124
  5. `/opsx-archive` — move the change to `openspec/changes/archive/`
125
+
126
+ When OpenSpec is used, `tasks.md` is the canonical implementation plan. Do not also run `ce-plan` for the same change.