@legioncodeinc/rflectr 0.1.0 → 0.1.1

package/README.md

@@ -43,11 +43,7 @@ Launch your tools, switch providers mid-session, and run local API gateways &mda
 
 <br>
 
-<picture>
-  <source media="(prefers-color-scheme: dark)" srcset="assets/rflectr-overview.png">
-  <source media="(prefers-color-scheme: light)" srcset="assets/rflectr-overview.png">
-  <img alt="rflectr — relay any model into any coding agent. You pick a coding tool, rflectr launches it and routes requests to any model provider you choose." src="assets/rflectr-overview.png" width="900">
-</picture>
+<img alt="rflectr — relay any model into any coding agent. You pick a coding tool, rflectr launches it and routes requests to any model provider you choose." src="https://github.com/legioncodeinc/rflectr/raw/cdaf2738d5e33e83a2c3b09d4bf604ef8426ca86/assets/733630021_1421561133353555_3999689754075308337_n.jpg" width="900">
 
 <br>
 <br>

package/dist/cli.js

@@ -35,7 +35,7 @@ import { join } from "path";
 // package.json
 var package_default = {
   name: "@legioncodeinc/rflectr",
-  version: "0.1.0",
+  version: "0.1.1",
   publishConfig: {
     access: "public"
   },

package/library/README.md

@@ -1,39 +1,39 @@
----
-ai_description: |
-  This is the root of the repository's documentation library (schema v2).
-  You own everything under library/ except notes/, which is human-only.
-  Sub-trees: knowledge/ (public and private docs), requirements/ (product
-  work: PRDs), issues/ (reactive bug/incident work: IRDs), notes/ (junk
-  drawer, read-only to agents).
-  Schema reference: legion-shared/standards/library-schema-v2.md.
-  Standardize script: pnpm standardize-library --repository <name>.
-human_description: |
-  Root of this repository's documentation library.
-  - knowledge/: reference documentation split by audience (public vs private)
-  - requirements/: planned product work (PRDs) with backlog/in-work/completed lifecycle
-  - issues/: reactive bug and incident work (IRDs) with same lifecycle
-  - notes/: unstructured scratch space — only humans write here
-  Run `pnpm standardize-library --repository <name>` to scaffold any missing structure.
----
-
-# Library
-
-Documentation root for this repository. Schema version: **v2**.
-
-See [`legion-shared/standards/library-schema-v2.md`](../../legion-shared/standards/library-schema-v2.md) for the full specification.
-
-## Top-level layout
-
-| Folder | What goes here |
-|---|---|
-| `knowledge/public/` | End-user / customer-facing docs: overviews, guides, FAQs |
-| `knowledge/private/` | Internal engineering and business docs: ADRs, standards, domain knowledge |
-| `requirements/` | Product and feature work: PRDs in backlog/in-work/completed |
-| `issues/` | Reactive bug and incident work: IRDs in backlog/in-work/completed |
-| `notes/` | Human-only scratch space |
-
-## What does NOT belong here
-
-- Brand assets → `legion-shared/brands/`
-- Wiki entity pages → `legion-wiki/<repo>/wiki/` (derived, never edit)
-- Library mirrors → `legion-wiki/<repo>/library/` (derived, never edit)
+---
+ai_description: |
+  This is the root of the repository's documentation library (schema v2).
+  You own everything under library/ except notes/, which is human-only.
+  Sub-trees: knowledge/ (public and private docs), requirements/ (product
+  work: PRDs), issues/ (reactive bug/incident work: IRDs), notes/ (junk
+  drawer, read-only to agents).
+  Schema reference: legion-shared/standards/library-schema-v2.md.
+  Standardize script: pnpm standardize-library --repository <name>.
+human_description: |
+  Root of this repository's documentation library.
+  - knowledge/: reference documentation split by audience (public vs private)
+  - requirements/: planned product work (PRDs) with backlog/in-work/completed lifecycle
+  - issues/: reactive bug and incident work (IRDs) with same lifecycle
+  - notes/: unstructured scratch space — only humans write here
+  Run `pnpm standardize-library --repository <name>` to scaffold any missing structure.
+---
+
+# Library
+
+Documentation root for this repository. Schema version: **v2**.
+
+See [`legion-shared/standards/library-schema-v2.md`](../../legion-shared/standards/library-schema-v2.md) for the full specification.
+
+## Top-level layout
+
+| Folder | What goes here |
+|---|---|
+| `knowledge/public/` | End-user / customer-facing docs: overviews, guides, FAQs |
+| `knowledge/private/` | Internal engineering and business docs: ADRs, standards, domain knowledge |
+| `requirements/` | Product and feature work: PRDs in backlog/in-work/completed |
+| `issues/` | Reactive bug and incident work: IRDs in backlog/in-work/completed |
+| `notes/` | Human-only scratch space |
+
+## What does NOT belong here
+
+- Brand assets → `legion-shared/brands/`
+- Wiki entity pages → `legion-wiki/<repo>/wiki/` (derived, never edit)
+- Library mirrors → `legion-wiki/<repo>/library/` (derived, never edit)

package/library/issues/README.md

@@ -1,46 +1,46 @@
----
-ai_description: |
-  This folder contains all reactive bug and incident work (IRDs).
-  It is a PEER of requirements/, not nested under it.
-  Sub-folders: backlog/, in-work/, completed/ — same lifecycle as requirements/.
-  IRD folder naming: ird-<###>-<kebab-slug>/
-  IRD numbers match the GitHub issue number for this repo.
-  Never invent IRD numbers — a GitHub issue must exist first.
-  IRDs are single-scope: one issue per IRD, no sub-IRDs.
-  Do NOT put PRDs here — those go in requirements/.
-human_description: |
-  Reactive bug and incident work (IRDs), organized by lifecycle stage.
-  - backlog/: tracked issues with a fix plan, not yet started
-  - in-work/: issues currently being fixed
-  - completed/: resolved issues (move entire folder)
-  IRD numbers match GitHub issue numbers. Create an IRD only after the
-  GitHub issue exists.
----
-
-# Issues
-
-Reactive bug and incident work (IRDs), organized by lifecycle state.
-
-## Sub-folders
-
-| Folder | State | Description |
-|---|---|---|
-| `backlog/` | Tracked | IRDs with a fix plan, not yet in progress |
-| `in-work/` | Active | Issues currently being resolved |
-| `completed/` | Resolved | Entire IRD folder moves here when the issue closes |
-
-## IRD folder structure
-
-```
-ird-042-stale-cache/
-  ird-042-stale-cache-index.md     single-scope fix plan
-  qa/
-    ird-042-stale-cache-qa.md      QA audit (written by quality-guardian)
-```
-
-## Naming rules
-
-- Folder: `ird-<###>-<kebab-slug>/`
-- Index: `ird-<###>-<kebab-slug>-index.md`
-- IRD number = GitHub issue number (never invented)
-- No sub-IRDs (scope one issue per IRD)
+---
+ai_description: |
+  This folder contains all reactive bug and incident work (IRDs).
+  It is a PEER of requirements/, not nested under it.
+  Sub-folders: backlog/, in-work/, completed/ — same lifecycle as requirements/.
+  IRD folder naming: ird-<###>-<kebab-slug>/
+  IRD numbers match the GitHub issue number for this repo.
+  Never invent IRD numbers — a GitHub issue must exist first.
+  IRDs are single-scope: one issue per IRD, no sub-IRDs.
+  Do NOT put PRDs here — those go in requirements/.
+human_description: |
+  Reactive bug and incident work (IRDs), organized by lifecycle stage.
+  - backlog/: tracked issues with a fix plan, not yet started
+  - in-work/: issues currently being fixed
+  - completed/: resolved issues (move entire folder)
+  IRD numbers match GitHub issue numbers. Create an IRD only after the
+  GitHub issue exists.
+---
+
+# Issues
+
+Reactive bug and incident work (IRDs), organized by lifecycle state.
+
+## Sub-folders
+
+| Folder | State | Description |
+|---|---|---|
+| `backlog/` | Tracked | IRDs with a fix plan, not yet in progress |
+| `in-work/` | Active | Issues currently being resolved |
+| `completed/` | Resolved | Entire IRD folder moves here when the issue closes |
+
+## IRD folder structure
+
+```
+ird-042-stale-cache/
+  ird-042-stale-cache-index.md     single-scope fix plan
+  qa/
+    ird-042-stale-cache-qa.md      QA audit (written by quality-guardian)
+```
+
+## Naming rules
+
+- Folder: `ird-<###>-<kebab-slug>/`
+- Index: `ird-<###>-<kebab-slug>-index.md`
+- IRD number = GitHub issue number (never invented)
+- No sub-IRDs (scope one issue per IRD)

package/library/issues/backlog/README.md

@@ -1,26 +1,26 @@
----
-ai_description: |
-  Contains IRD folders for tracked issues not yet in active fix work.
-  Create a new IRD here only AFTER the GitHub issue exists for this repo.
-  IRD folder: ird-<###>-<slug>/ where ### = GitHub issue number.
-  Must contain: ird-<###>-<slug>-index.md (the fix plan) and qa/ folder.
-  IRDs are single-scope: do not add sub-IRDs.
-human_description: |
-  IRDs planned but not yet in active fix work. Create IRDs here.
-  - Naming: ird-042-stale-cache/ with ird-042-stale-cache-index.md inside
-  - IRD number must match the GitHub issue number
-  - Create only after the GitHub issue exists
-  Move to in-work/ when fix work begins.
----
-
-# Issues — Backlog
-
-Tracked issues with a fix plan, not yet in active resolution.
-
-## Creating a new IRD
-
-1. Confirm the GitHub issue number (e.g., #42).
-2. Create `ird-042-<kebab-slug>/`.
-3. Create `ird-042-<slug>-index.md` — the single-scope fix plan.
-4. Create `qa/` subfolder (empty; `quality-guardian` writes here).
-5. No sub-IRDs — keep scope to one issue.
+---
+ai_description: |
+  Contains IRD folders for tracked issues not yet in active fix work.
+  Create a new IRD here only AFTER the GitHub issue exists for this repo.
+  IRD folder: ird-<###>-<slug>/ where ### = GitHub issue number.
+  Must contain: ird-<###>-<slug>-index.md (the fix plan) and qa/ folder.
+  IRDs are single-scope: do not add sub-IRDs.
+human_description: |
+  IRDs planned but not yet in active fix work. Create IRDs here.
+  - Naming: ird-042-stale-cache/ with ird-042-stale-cache-index.md inside
+  - IRD number must match the GitHub issue number
+  - Create only after the GitHub issue exists
+  Move to in-work/ when fix work begins.
+---
+
+# Issues — Backlog
+
+Tracked issues with a fix plan, not yet in active resolution.
+
+## Creating a new IRD
+
+1. Confirm the GitHub issue number (e.g., #42).
+2. Create `ird-042-<kebab-slug>/`.
+3. Create `ird-042-<slug>-index.md` — the single-scope fix plan.
+4. Create `qa/` subfolder (empty; `quality-guardian` writes here).
+5. No sub-IRDs — keep scope to one issue.

package/library/issues/completed/README.md

@@ -1,13 +1,13 @@
----
-ai_description: |
-  Resolved IRD folders. Entire ird-<###>-<slug>/ folders move here from
-  in-work/ when the corresponding GitHub issue is closed and verified.
-  Read-only after landing — do NOT edit or re-open IRDs here.
-human_description: |
-  Resolved issue folders. Move entire ird-NNN-slug/ here from in-work/
-  when the GitHub issue is closed and the fix is confirmed. Read-only.
----
-
-# Issues — Completed
-
-Resolved IRD folders. Entire `ird-<###>-<slug>/` folders land here when the GitHub issue closes and the fix is confirmed. Do not edit files here after landing.
+---
+ai_description: |
+  Resolved IRD folders. Entire ird-<###>-<slug>/ folders move here from
+  in-work/ when the corresponding GitHub issue is closed and verified.
+  Read-only after landing — do NOT edit or re-open IRDs here.
+human_description: |
+  Resolved issue folders. Move entire ird-NNN-slug/ here from in-work/
+  when the GitHub issue is closed and the fix is confirmed. Read-only.
+---
+
+# Issues — Completed
+
+Resolved IRD folders. Entire `ird-<###>-<slug>/` folders land here when the GitHub issue closes and the fix is confirmed. Do not edit files here after landing.

package/library/issues/in-work/README.md

@@ -1,13 +1,13 @@
----
-ai_description: |
-  IRD folders actively being resolved. Mirror of requirements/in-work/
-  but for issues. Move entire ird-<###>-<slug>/ folder from backlog/
-  here when fix work begins, then to completed/ when the issue closes.
-human_description: |
-  IRDs currently being fixed. Move folder from backlog/ here when work
-  starts, and to completed/ when the GitHub issue is closed.
----
-
-# Issues — In Work
-
-IRDs currently being resolved. Move from `backlog/` → here when fix work starts, then `completed/` when the GitHub issue closes.
+---
+ai_description: |
+  IRD folders actively being resolved. Mirror of requirements/in-work/
+  but for issues. Move entire ird-<###>-<slug>/ folder from backlog/
+  here when fix work begins, then to completed/ when the issue closes.
+human_description: |
+  IRDs currently being fixed. Move folder from backlog/ here when work
+  starts, and to completed/ when the GitHub issue is closed.
+---
+
+# Issues — In Work
+
+IRDs currently being resolved. Move from `backlog/` → here when fix work starts, then `completed/` when the GitHub issue closes.

package/library/knowledge/README.md

@@ -1,34 +1,34 @@
----
-ai_description: |
-  This folder contains all reference documentation for this repository,
-  split by intended audience: public/ for end-users, private/ for internal
-  team and AI agents. When filing a new doc, default to private/. Promote
-  to public/ only when the content is intentionally customer-facing.
-  Allowed writes: knowledge/public/<domain>/<slug>.md and
-  knowledge/private/<domain>/<slug>.md. ADRs always go in
-  knowledge/private/architecture/ADR-<n>-<slug>.md.
-  Never write to knowledge/ itself (write to the sub-folders).
-human_description: |
-  Reference documentation split by audience.
-  - public/: docs that will eventually be surfaced to customers or published
-  - private/: internal engineering, architecture, business, and strategy docs
-  When adding a new doc, pick the right subdomain folder inside public/ or
-  private/. If the domain doesn't exist yet, create it.
----
-
-# Knowledge
-
-Reference documentation for this repository, organized by audience.
-
-## Sub-folders
-
-| Folder | Audience | Typical content |
-|---|---|---|
-| `public/` | End-users, customers, external | Overviews, user guides, FAQs |
-| `private/` | Internal team + AI agents | ADRs, standards, architecture, domain engineering docs |
-
-## Decision rule: public vs private
-
-> "Would I publish this on a help center or product docs site?"
-
-Yes → `public/`. No → `private/`. When in doubt, `private/`.
+---
+ai_description: |
+  This folder contains all reference documentation for this repository,
+  split by intended audience: public/ for end-users, private/ for internal
+  team and AI agents. When filing a new doc, default to private/. Promote
+  to public/ only when the content is intentionally customer-facing.
+  Allowed writes: knowledge/public/<domain>/<slug>.md and
+  knowledge/private/<domain>/<slug>.md. ADRs always go in
+  knowledge/private/architecture/ADR-<n>-<slug>.md.
+  Never write to knowledge/ itself (write to the sub-folders).
+human_description: |
+  Reference documentation split by audience.
+  - public/: docs that will eventually be surfaced to customers or published
+  - private/: internal engineering, architecture, business, and strategy docs
+  When adding a new doc, pick the right subdomain folder inside public/ or
+  private/. If the domain doesn't exist yet, create it.
+---
+
+# Knowledge
+
+Reference documentation for this repository, organized by audience.
+
+## Sub-folders
+
+| Folder | Audience | Typical content |
+|---|---|---|
+| `public/` | End-users, customers, external | Overviews, user guides, FAQs |
+| `private/` | Internal team + AI agents | ADRs, standards, architecture, domain engineering docs |
+
+## Decision rule: public vs private
+
+> "Would I publish this on a help center or product docs site?"
+
+Yes → `public/`. No → `private/`. When in doubt, `private/`.

package/library/knowledge/private/README.md

@@ -1,40 +1,40 @@
----
-ai_description: |
-  This folder contains internal engineering and business documentation.
-  ADRs MUST live in architecture/ADR-<n>-<kebab-slug>.md.
-  Engineering standards MUST live in standards/documentation-framework.md.
-  Other domain folders (<domain>/) are repo-specific and may be created as
-  needed (ai/, auth/, data/, frontend/, infrastructure/, integrations/,
-  marketing/, operations/, personas/, reporting/, roadmap/, scanners/,
-  security/, strategy/, etc.).
-  Do NOT file customer-facing content here (that goes in knowledge/public/).
-  Write path: library/knowledge/private/<domain>/<kebab-slug>.md.
-human_description: |
-  Internal engineering and business documentation.
-  - architecture/: Architecture Decision Records (ADRs)
-  - standards/: Documentation framework and coding standards
-  - <domain>/: Any repo-specific knowledge domain (ai/, auth/, data/, etc.)
-  Default landing zone for any doc that does not need to be customer-facing.
-  When creating a new domain folder, add a README.md explaining what belongs.
----
-
-# Knowledge — Private
-
-Internal documentation for engineers, product, and AI agents.
-
-## Required sub-folders (always present)
-
-| Folder | Contents |
-|---|---|
-| `architecture/` | ADRs: `ADR-<n>-<kebab-slug>.md`. Locked decisions with context, alternatives, consequences. |
-| `standards/` | `documentation-framework.md` and any repo-specific writing rules. |
-
-## Optional domain folders
-
-Create any of these as needed: `ai/`, `auth/`, `data/`, `frontend/`, `infrastructure/`, `integrations/`, `marketing/`, `operations/`, `personas/`, `reporting/`, `roadmap/`, `scanners/`, `security/`, `strategy/`, `reference/`, `<product>-ux-ui/`.
-
-## What does NOT belong here
-
-- Customer-facing content (put in `knowledge/public/`)
-- PRDs or IRDs (put in `requirements/` or `issues/`)
-- Brand assets (put in `legion-shared/brands/`)
+---
+ai_description: |
+  This folder contains internal engineering and business documentation.
+  ADRs MUST live in architecture/ADR-<n>-<kebab-slug>.md.
+  Engineering standards MUST live in standards/documentation-framework.md.
+  Other domain folders (<domain>/) are repo-specific and may be created as
+  needed (ai/, auth/, data/, frontend/, infrastructure/, integrations/,
+  marketing/, operations/, personas/, reporting/, roadmap/, scanners/,
+  security/, strategy/, etc.).
+  Do NOT file customer-facing content here (that goes in knowledge/public/).
+  Write path: library/knowledge/private/<domain>/<kebab-slug>.md.
+human_description: |
+  Internal engineering and business documentation.
+  - architecture/: Architecture Decision Records (ADRs)
+  - standards/: Documentation framework and coding standards
+  - <domain>/: Any repo-specific knowledge domain (ai/, auth/, data/, etc.)
+  Default landing zone for any doc that does not need to be customer-facing.
+  When creating a new domain folder, add a README.md explaining what belongs.
+---
+
+# Knowledge — Private
+
+Internal documentation for engineers, product, and AI agents.
+
+## Required sub-folders (always present)
+
+| Folder | Contents |
+|---|---|
+| `architecture/` | ADRs: `ADR-<n>-<kebab-slug>.md`. Locked decisions with context, alternatives, consequences. |
+| `standards/` | `documentation-framework.md` and any repo-specific writing rules. |
+
+## Optional domain folders
+
+Create any of these as needed: `ai/`, `auth/`, `data/`, `frontend/`, `infrastructure/`, `integrations/`, `marketing/`, `operations/`, `personas/`, `reporting/`, `roadmap/`, `scanners/`, `security/`, `strategy/`, `reference/`, `<product>-ux-ui/`.
+
+## What does NOT belong here
+
+- Customer-facing content (put in `knowledge/public/`)
+- PRDs or IRDs (put in `requirements/` or `issues/`)
+- Brand assets (put in `legion-shared/brands/`)