@storybloq/storybloq 1.4.2 → 1.4.4
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/README.md +2 -0
- package/dist/cli.js +489 -147
- package/dist/index.d.ts +12 -3
- package/dist/index.js +23 -19
- package/dist/mcp.js +49 -45
- package/package.json +1 -1
- package/src/skill/SKILL.md +8 -9
package/README.md
CHANGED
|
@@ -355,6 +355,8 @@ Full type definitions ship with the package (`exports.types`).
|
|
|
355
355
|
|
|
356
356
|
Each record is its own file. IDs are sequential within type (`T-001`, `T-002`, ...). Relationships are single-canonical-owner: a ticket's `blockedBy` field points at blocker tickets, and the reverse (who-blocks-me) is derived by scanning.
|
|
357
357
|
|
|
358
|
+
Create operations are safe to run in parallel. ID assignment and the create write happen together under a project lock, so concurrent creators are serialized and each receives a distinct sequential ID. A create can never silently overwrite an existing record; under heavy simultaneous contention a creator fails loudly with an error rather than colliding.
|
|
359
|
+
|
|
358
360
|
Ticket and issue records preserve unknown JSON fields. Use `storybloq ticket meta` and `storybloq issue meta` to read or mutate those custom passthrough fields without touching core Storybloq fields. Values are JSON, and dot paths address nested objects, for example `storybloq ticket meta set T-001 integration.linear '"ABC-123"'`.
|
|
359
361
|
|
|
360
362
|
## Example workflow
|