billion-context-pi 0.0.4 → 0.0.6

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/package.json CHANGED
@@ -1,7 +1,7 @@
1
1
  {
2
2
  "name": "billion-context-pi",
3
- "version": "0.0.4",
4
- "description": "Active Context Pruning (ACP) extension for Pi \u2014 model-driven context compression that keeps conversations flowing.",
3
+ "version": "0.0.6",
4
+ "description": "One billion, not one million. Model-driven context management for the Pi coding agent.",
5
5
  "main": "dist/index.js",
6
6
  "types": "dist/index.d.ts",
7
7
  "exports": {
@@ -21,10 +21,10 @@
21
21
  "LICENSE"
22
22
  ],
23
23
  "sideEffects": false,
24
- "homepage": "https://github.com/ranxianglei/pai-acp#readme",
24
+ "homepage": "https://github.com/ranxianglei/billion-context-pi",
25
25
  "repository": {
26
26
  "type": "git",
27
- "url": "git+https://github.com/ranxianglei/pai-acp.git"
27
+ "url": "git+https://github.com/ranxianglei/billion-context-pi.git"
28
28
  },
29
29
  "bugs": {
30
30
  "url": "https://github.com/ranxianglei/pai-acp/issues"
@@ -1,14 +0,0 @@
1
- /** SYNC: is the running package the legacy pai-acp? Used by the factory to
2
- * decide whether self-disable logic applies. */
3
- export declare function isLegacyPackage(): boolean;
4
- /** SYNC: has billion-context-pi been installed AND is it loadable?
5
- * Checks both package.json AND dist/index.js to avoid a partial install
6
- * (package.json written but dist missing) self-disabling the legacy package
7
- * before the new one can load — which would leave the user with no ACP tools. */
8
- export declare function isNewPackageInstalled(): boolean;
9
- /** Called from session_start of the LEGACY package (only). If the new package
10
- * has a real release on npm, installs it and notifies the user to restart.
11
- * The legacy package then self-disables on the next launch (factory detects
12
- * the new package in node_modules and registers nothing). Until a real
13
- * release exists, shows a friendly manual notice. */
14
- export declare function checkRename(notify: (msg: string) => void): Promise<void>;