repo-nexus 0.3.1 → 0.3.4

package/README.md

@@ -54,7 +54,7 @@ A **simple, lightweight companion tool** for multi-repo workflows. It links mult
 
 ```
 ┌─────────────────────────────────────────────────────────────┐
-│  Repo Nexus Workspace Root                                 │
+│  Repo Nexus Workspace Root                                  │
 │                                                             │
 │  my-workspace/                                              │
 │    repos/                                                   │
@@ -93,22 +93,25 @@ A **simple, lightweight companion tool** for multi-repo workflows. It links mult
 
 ## Installation
 
-Install `rnex` via npm, GitHub Packages, or the zero-dependency native installer:
+Install `rnex` via npm, standalone one-liner (`curl` / `wget`), or from source:
 
-### Option 1: Via npm (Recommended)
+### Option 1: Via npm (Global)
 
 ```bash
 npm install -g repo-nexus
 ```
-*(Installs both `repo-nexus` and `rnex` commands globally, or run via `npx repo-nexus init`)*
+*(Installs both `repo-nexus` and `rnex` commands globally, or run without installing via `npx repo-nexus init`)*
 
-### Option 2: Via GitHub Packages
+### Option 2: Standalone One-Liner (curl / wget — Zero Dependencies, No Node.js)
 
 ```bash
-npm install -g @nu-nenoi/repo-nexus --registry=https://npm.pkg.github.com
+curl -fsSL https://raw.githubusercontent.com/nu-nenoi/repo-nexus/main/scripts/install.sh | sh
+# or
+wget -qO- https://raw.githubusercontent.com/nu-nenoi/repo-nexus/main/scripts/install.sh | sh
 ```
+*(Downloads and links `rnex` and `repo-nexus` into `~/.local/bin` without requiring Node.js or npm)*
 
-### Option 3: Native Installer (Zero Dependencies)
+### Option 3: Native Installer (Clone & Install)
 
 Clone the repository and run the built-in installer:
 
@@ -144,7 +147,7 @@ rnex add frontend ../web-app          # relative paths work too
 rnex status
 ```
 
-During `rnex init`, the CLI automatically scans for existing AI configuration files (like `CLAUDE.md`, `.cursorrules`, `.github/copilot-instructions.md`) and adds them to your config.
+During `rnex init`, the CLI creates `rnex.yaml` if none exists for the directory, and merges Repo Nexus workspace instructions with any existing AI instructions (such as `AGENTS.md`, `CLAUDE.md`, `.cursorrules`).
 
 ---
 
@@ -211,20 +214,22 @@ The `karpathy-llm` plugin packages Andrej Karpathy's verified LLM agent design p
 * **Autonomous Karpathy LLM Wiki Knowledge Architecture:**
   * **Intake (`/raw/`):** Append-only intake for unmodified source documents.
   * **Curated Knowledge Base (`/wiki/`):** Interlinked atomic markdown pages with typed YAML frontmatter relations (`sources`, `related`, `extends`, `contradicts`, `mentioned_in`).
-  * **Control Index (`/wiki/index.md`):** Master navigation index with `lint_trigger: enabled|disabled` toggle.
+  * **Navigation Index (`/wiki/index.md`):** Master categorized navigation index.
   * **Rolling Context (`/wiki/hot.md`):** ~500-word quick-orient context cache for AI agents.
   * **Operation Log (`/wiki/_log.md`):** Append-only audit trail of ingest and lint operations.
-  * **Session Counter (`.rnex/.lint_trigger_counter`):** Machine-local state tracking session activity (gitignored).
-* **Autonomous Lint Trigger (`.rnex/scripts/wiki-lint-trigger.sh`):** Session counter and maintenance alerts on session 1 and every 15 sessions.
 * **Standardized Workflows (`.rnex/workflows/`):**
   * `wiki-ingest.md`: 8-step protocol decomposing raw source documents into 5–25 atomic wiki pages.
   * `wiki-lint.md`: 10-step protocol validating paths, recomputing `mentioned_in`, removing orphans, resolving contradictions, identifying gaps, suggesting source candidates, and rebuilding indexes.
 
 ---
 
-## Workspace Configuration (`rnex.yaml`)
+## Two-Level Configuration
 
-The configuration file defines repo symlink directory, enabled plugins, and registered repositories:
+Repo Nexus supports a two-level configuration model:
+1. **Repo Config (`rnex.yaml`):** Shared manifest committed to git. Tracks member repo names, default settings, and active plugins.
+2. **Local Config (`.local.rnex.yaml`):** Machine-specific file ignored in `.gitignore`. Overrides or provides member repo paths on each developer's workstation.
+
+### Repo Configuration (`rnex.yaml`)
 
 ```yaml
 # Directory for repository symlinks (relative or absolute)
@@ -232,17 +237,15 @@ repos_dir: ./repos
 
 # Workspace plugins
 plugins:
-  karpathy-llm:
-    lint_trigger_enabled: true
+  karpathy-llm: {}
 
 # Member repositories
 repos:
   backend:
-    path: /Users/dev/code/backend-api
     scope: visible
     rnex_dir: true      # default: true (creates repos/backend/.rnex/)
   frontend:
-    path: ../web-app
+    path: ../web-app    # optional default relative path
     scope: visible
     rnex_dir: true
   analytics:
@@ -251,6 +254,14 @@ repos:
     rnex_dir: false     # disabled: leaves analytics repo 100% untouched
 ```
 
+### Local Configuration (`.local.rnex.yaml`)
+
+```yaml
+repos:
+  backend:
+    path: /Users/alice/projects/backend-api
+```
+
 > See [`docs/rnex.example.yaml`](docs/rnex.example.yaml) for a comprehensive example with all options.
 > For common questions and architecture details, see the [Frequently Asked Questions (FAQ)](docs/FAQ.md).
 

package/docs/AGENTS.sample.md

@@ -4,8 +4,10 @@ This workspace operates as a **Repo Nexus** linking multiple independent reposit
 
 ## Rules for AI Coding Assistants
 
-1. **Symlink Write-Through**: Files edited under `repos/<name>/` directly modify the target repository.
-2. **Repo Boundaries**: Each repository is isolated. Do not introduce cross-repo imports unless explicitly architected.
-3. **Shared Context**: This file governs AI assistant behavior across all member repositories. Keep instructions universal. Use local instructions for repo-specific rules.
-4. **Member Repo RNEX Context**: Member repositories may contain an `.rnex/` directory (accessible via `repos/<name>/.rnex/`) containing repository-specific documents, instructions, rules, workflows, and scripts managed by Repo Nexus. AI assistants operating at the workspace level MUST inspect `repos/<name>/.rnex/` for member-specific context, guidelines, and commands.
-5. **Git Operations**: Commit and push changes directly within the respective member repository root.
+1. **Workspace Structure & Settings**: AI coding assistants MUST inspect and read `rnex.yaml` at the workspace root to understand the workspace structure (such as `repos_dir`), registered member repositories, and active configuration settings.
+2. **Symlink Write-Through**: Files edited under `repos/<name>/` directly modify the target repository.
+3. **Repo Boundaries**: Each repository is isolated. Do not introduce cross-repo imports unless explicitly architected.
+4. **Shared Context**: This file governs AI assistant behavior across all member repositories. Keep instructions universal. Use local instructions for repo-specific rules.
+5. **Member Repo RNEX Context**: Member repositories may contain an `.rnex/` directory (accessible via `repos/<name>/.rnex/`) containing repository-specific documents, instructions, rules, workflows, and scripts managed by Repo Nexus. AI assistants operating at the workspace level MUST inspect `repos/<name>/.rnex/` for member-specific context, guidelines, and commands.
+6. **Plugin Instructions**: If plugins are enabled in `rnex.yaml` (under `plugins:`), AI coding assistants MUST read instructions for each enabled plugin from its separate instruction files (located in `.rnex/instructions/` or `.rnex/rules/`).
+7. **Git Operations**: Commit and push changes directly within the respective member repository root.

package/docs/rnex.example.yaml

@@ -1,7 +1,13 @@
 # ==============================================================================
 # rnex.yaml — Repo Nexus Workspace Configuration (Full Example)
 # ==============================================================================
-# This file is the central manifest for a Repo Nexus workspace.
+# This file is the central team manifest for a Repo Nexus workspace (committed to git).
+#
+# TWO-LEVEL CONFIGURATION:
+#   1. Repo Config (rnex.yaml): Shared across team, tracks member repos, plugins.
+#   2. Local Config (.local.rnex.yaml): Machine-specific (gitignored), overrides/provides
+#      local member repo paths and developer-specific plugin settings.
+#
 # Place it in your workspace root directory and run `rnex sync` to apply.
 #
 # For more information: https://github.com/nu-nenoi/repo-nexus
@@ -37,8 +43,7 @@ repos_dir: ./repos
 # Local / custom plugins can also be placed in .rnex/plugins/<name>/
 
 plugins:
-  # karpathy-llm:
-  #   lint_trigger_enabled: true
+  # karpathy-llm: {}
 
 # ------------------------------------------------------------------------------
 # repos — Member repositories managed by Repo Nexus

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "repo-nexus",
-  "version": "0.3.1",
+  "version": "0.3.4",
   "description": "Lightweight, zero-dependency companion tool for multi-repo workspaces and shared AI context via symlinks (no git submodules)",
   "bin": {
     "repo-nexus": "rnex",