pi-footer-manager 1.0.0 → 1.0.2

package/README.md

@@ -4,6 +4,26 @@ One footer, many extensions: build flexible Pi footers from reusable fragments w
 
 `pi-footer-manager` lets one extension own `ctx.ui.setFooter(...)` while built-in and custom fragments are arranged through a shared API, with flexible rows, regions, widths, alignment, and redraw/invalidation flow.
 
+## Install or test
+
+Install permanently:
+
+```bash
+pi install npm:pi-footer-manager
+```
+
+Test without installing permanently:
+
+```bash
+pi --no-extensions -e npm:pi-footer-manager
+```
+
+To load it alongside your normal setup:
+
+```bash
+pi -e npm:pi-footer-manager
+```
+
 ![pi-footer-manager screenshot](./assets/pi-footer-manager.png)
 
 ## Included extensions
@@ -14,6 +34,20 @@ One footer, many extensions: build flexible Pi footers from reusable fragments w
 - `fragments/quota-footer-fragment-text.ts` — text-focused quota usage display
 - `fragments/context-gauge-text-fragment.ts` — text version of context usage
 
+## Public API for custom fragment extensions
+
+External extensions can integrate with the footer manager through:
+
+```ts
+import {
+  FOOTER_MANAGER_REGISTER_FRAGMENT,
+  FOOTER_MANAGER_UNREGISTER_FRAGMENT,
+  type FooterFragmentRegistration,
+} from "pi-footer-manager/api";
+```
+
+This is the supported public integration surface for custom fragment extensions. It avoids fragile cross-extension relative imports and lets third-party fragment extensions live in their own repos or packages.
+
 ## How configuration works
 
 Layout is configured under `footerManager.layout` in Pi settings.
@@ -164,6 +198,8 @@ See detailed fragment API docs and examples in:
 
 - [`footer-manager/README.md`](./footer-manager/README.md)
 
+The public integration module for external fragment extensions is `pi-footer-manager/api`.
+
 ## Check
 
 ```bash

package/footer-manager/README.md

@@ -10,7 +10,7 @@ It calls `ctx.ui.setFooter(...)` once, while other extensions contribute footer
 import {
   FOOTER_MANAGER_REGISTER_FRAGMENT,
   type FooterFragmentRegistration,
-} from "./footer-manager/types";
+} from "pi-footer-manager/api";
 
 export default function (pi) {
   pi.on("session_start", async () => {
@@ -41,6 +41,8 @@ pi.events.emit("footer-manager:invalidate", { id: "my-extension.timer" });
 
 Invalidations are coalesced and the manager owns `tui.requestRender()`.
 
+For external extensions, `pi-footer-manager/api` is the supported integration surface. It exports the fragment event names and the main fragment/layout types without requiring fragile cross-extension relative imports.
+
 ## Layout configuration
 
 Settings live under `footerManager.layout`.

package/footer-manager/api.ts

@@ -0,0 +1,17 @@
+export {
+  FOOTER_MANAGER_REGISTER_FRAGMENT,
+  FOOTER_MANAGER_UNREGISTER_FRAGMENT,
+  FOOTER_MANAGER_INVALIDATE,
+} from "./types.js";
+
+export type {
+  FooterFragmentRegistration,
+  FooterRenderEnv,
+  FooterFragmentComponent,
+  FooterRegionAlign,
+  FooterRegionWidth,
+  FooterRegionConfig,
+  FooterRowConfig,
+  FooterLayoutConfig,
+  FooterManagerSettings,
+} from "./types.js";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-footer-manager",
-  "version": "1.0.0",
+  "version": "1.0.2",
   "description": "One footer, many extensions: build flexible Pi footers from reusable fragments with configurable layout and built-in fragments instead of competing `setFooter()` calls. `pi-footer-manager` lets one extension own footer rendering while built-in and custom fragments are arranged through a shared API and flexible layout system.",
   "type": "module",
   "keywords": [
@@ -9,7 +9,10 @@
     "extension",
     "footer-manager"
   ],
-  "exports": "./footer-manager/index.ts",
+  "exports": {
+    ".": "./footer-manager/index.ts",
+    "./api": "./footer-manager/api.ts"
+  },
   "files": [
     "footer-manager",
     "fragments",