@thebassclef/lite 1.9.1 → 1.9.2

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 CHANGED
@@ -9,6 +9,8 @@ bassclef init
9
9
 
10
10
  Five minutes from install to a working bassclef in your repo.
11
11
 
12
+ **New here?** Read [docs.bassclef.dev](https://docs.bassclef.dev) for the full guide — what bassclef is, how to onboard your repo, what each skill does.
13
+
12
14
  ## What it does
13
15
 
14
16
  `bassclef init` writes a small set of files into your project — a
@@ -19,6 +21,13 @@ and agents on the next Claude Code session.
19
21
  `bassclef sync` upgrades those files in place when a newer package
20
22
  version publishes.
21
23
 
24
+ ### What `bassclef sync` touches
25
+
26
+ If you want to know exactly what gets written to your repo before you
27
+ run it — see [docs.bassclef.dev/docs/config/substrate-config](https://docs.bassclef.dev/docs/config/substrate-config).
28
+ Short version — the file list is bounded to `.claude/`, `docs/whereami.md`,
29
+ and the project manifest. Nothing outside that footprint moves.
30
+
22
31
  ## Supported systems
23
32
 
24
33
  - **macOS** — first-class. Every release is tested here.
@@ -33,11 +42,37 @@ See [`standards/os-support.md`](standards/os-support.md) for the full policy.
33
42
  - Node.js 20 or newer.
34
43
  - npm 10 or newer.
35
44
 
45
+ ## Hit a red BLOCKED banner?
46
+
47
+ Bassclef fires BLOCKED banners at the start of a session when a check
48
+ does not pass. Most banners come with a "how to fix" line right in the
49
+ banner text. Read that line first — it names the file or command that
50
+ resolves the block.
51
+
52
+ Still stuck? Check the [troubleshooting page](https://docs.bassclef.dev/docs/architecture/failure-mode)
53
+ on the docs site, or [file a bug](#file-a-bug-or-ask-a-question) below.
54
+
55
+ ## File a bug or ask a question
56
+
57
+ - **Something broke** — [open a bug report](https://github.com/sunj-labs/bassclef-cli/issues/new?template=bug_report.md).
58
+ - **Question about how it works** — [open a question](https://github.com/sunj-labs/bassclef-cli/issues/new?template=question.md).
59
+ - **Idea for a feature** — [open a feature request](https://github.com/sunj-labs/bassclef-cli/issues/new?template=feature_request.md).
60
+
61
+ `npm bugs @thebassclef/lite` also works — it opens the issue tracker in
62
+ your browser.
63
+
36
64
  ## Current release
37
65
 
38
- <!-- version-start -->1.9.1<!-- version-end -->
66
+ <!-- version-start -->1.9.2<!-- version-end -->
67
+
68
+ See [CHANGELOG.md](CHANGELOG.md) for the full changelog. Adopter-facing
69
+ release notes live at [docs.bassclef.dev/docs/whats-new/releases](https://docs.bassclef.dev/docs/whats-new/releases).
70
+
71
+ ## Community + security
39
72
 
40
- See [CHANGELOG.md](CHANGELOG.md) for release notes.
73
+ - [Code of Conduct](CODE_OF_CONDUCT.md) — how we treat each other in issues + PRs.
74
+ - [Security policy](SECURITY.md) — how to report a vulnerability privately.
75
+ - [Contributing](CONTRIBUTING.md) — how to send a PR.
41
76
 
42
77
  ## License
43
78
 
package/dist/index.cjs CHANGED
@@ -1,4 +1,4 @@
1
1
  "use strict";
2
2
  Object.defineProperty(exports, Symbol.toStringTag, { value: "Module" });
3
- const version = "1.9.1";
3
+ const version = "1.9.2";
4
4
  exports.version = version;
package/dist/index.d.ts CHANGED
@@ -1,2 +1,2 @@
1
- export declare const version: "1.9.1";
1
+ export declare const version: "1.9.2";
2
2
  //# sourceMappingURL=index.d.ts.map
package/dist/index.js CHANGED
@@ -1,4 +1,4 @@
1
- const version = "1.9.1";
1
+ const version = "1.9.2";
2
2
  export {
3
3
  version
4
4
  };