@svayam-opensource/prj 0.5.1

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Svayam Infoware Private Limited and contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,123 @@
+# Agentic Development Framework !!
+
+A governance-first framework for organizing agentic software development inside an organization. It provides a directory structure, a policy template, a CLI, and a set of scripts that enforce the policy through every step of a project's lifecycle — so AI agents and human developers can work in parallel on multiple projects without losing track of who owns what, what's been decided, and what changed.
+
+This repository is a **template**. Clone it, configure `org-config.yaml` with your organization's values, run `setup.sh`, and you have a workspace repo for your org's agentic development.
+
+---
+
+## Why this exists
+
+Agentic development gets messy fast: agents make decisions, modify multiple repos in parallel, propose policy updates, and accumulate institutional knowledge. Most teams handle this with ad-hoc convention; that breaks down past a handful of projects or a few agents.
+
+This framework gives you:
+
+- **Identifiable units of work** — every project gets a sequential, immutable ID (e.g., `ACME-001-invoice-api`); branches and folders derive from it.
+- **Layered knowledge** — org-wide policy, project-specific learnings, repo-local conventions, and developer preferences, with explicit precedence rules.
+- **Test-merge gate** — schema, registry, lifecycle, and cross-reference validators run locally before any merge to your default branch and again in CI on every PR. The default branch is hard to corrupt by accident.
+- **Compliance levels** — three tiers (Non-Negotiable, Always Apply, Apply Intelligently) so policy can distinguish between hard rules and judgment calls.
+- **One CLI** — `prj` wraps the whole lifecycle: seed, task, merge, pause, resume, sync, close, propose-knowledge.
+- **Knowledge close** — completed projects produce reviewed proposals to update org knowledge, so learnings flow back upstream.
+
+---
+
+## Quickstart
+
+> This is a **template repository.** You don't fork it — you use it to scaffold *your own* private workspace repo, which you then own and commit to. The framework's `publish` upstream stays clean; your private overlay (real projects, accumulated knowledge, your `org-config.yaml` values) lives only in your repo.
+
+**1. Create your repo from the template.** Open the framework's repo on GitHub:
+
+> https://github.com/svayam-opensource/governed-agentic-dev-framework
+
+Click the green **"Use this template"** button → **"Create a new repository"**. Pick a name (e.g. `000-acme-prj`) and visibility (typically Private). GitHub will create a new repository under your account or org.
+
+**2. Clone *your* new repo and run the setup.**
+
+```bash
+# Clone YOUR new repository (not this template).
+git clone https://github.com/<your-github-org>/<your-new-repo>.git
+cd <your-new-repo>
+
+# Verify the toolchain (git, gh, python3, pyyaml; yq optional).
+# Hard gate — refuses to proceed if anything required is missing.
+bash scripts/install-deps.sh
+
+# Configure the framework for your org and verify GitHub access.
+# Interactive: prompts for org name, slug, role identities, etc., with
+# sensible defaults detected from gh and git config. Substitutes
+# throughout, then checks gh user / org membership / scopes.
+bash setup.sh
+
+# (Optional) Customize the policy text for your org.
+$EDITOR knowledge/policies/agentic-development-policy.md
+
+# Commit and push to YOUR repository.
+git add -A
+git commit -m "configure framework for <your-org>"
+git push origin main
+
+# Start using it.
+./prj
+```
+
+The `prj` CLI is interactive: it lists current projects, walks you through seeding new ones, creating tasks, and closing them.
+
+**Re-running `setup.sh` later** is safe — it remembers your existing values as defaults. Use `bash setup.sh --non-interactive` in CI or scripts to skip prompts entirely.
+
+---
+
+## Concepts at a glance
+
+- **Workspace repo** — this repository. Holds policy, project manifests, and accumulated knowledge. Not a code repo.
+- **Project** — a unit of work with an ID, an assignee, a lifecycle (proposed → active → paused/completed/cancelled), and one or more code repos it touches.
+- **Knowledge layers** (highest to lowest priority): org-wide → project → repo-local → developer preferences. Higher always wins.
+- **Compliance levels** — C01 (Non-Negotiable, hard stop), C02 (Always Apply, exception PR required), C03 (Apply Intelligently, document deviation).
+- **Test-merge gate** — local validators run before any push to the default branch; CI runs the same validators on every PR.
+
+Full details in [docs/USER_GUIDE.md](docs/USER_GUIDE.md).
+
+---
+
+## Documentation
+
+| Doc | For |
+|---|---|
+| [README](README.md) | First-time visitor — what this is, do you want it |
+| [docs/USER_GUIDE.md](docs/USER_GUIDE.md) | Reference — concepts, roles, CLI surface |
+| [docs/DEVELOPER_GUIDE.md](docs/DEVELOPER_GUIDE.md) | Day-in-the-life — step-by-step working on a project, prompting the agent |
+| [CONTRIBUTING.md](CONTRIBUTING.md) | Contributor — proposing changes to the framework itself |
+| [SECURITY.md](SECURITY.md) | Security reporter |
+| [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md) | Community standards |
+| [knowledge/policies/agentic-development-policy.md](knowledge/policies/agentic-development-policy.md) | The policy itself — read this once you've adopted |
+
+---
+
+## Scripts and CLI
+
+| Tool | Purpose |
+|---|---|
+| `./prj` | Interactive CLI — wraps everything below |
+| `scripts/seed.sh` | Seed a new project (sets ID, scaffolds folder, creates branches) |
+| `scripts/create-task.sh` / `merge-task.sh` | Sub-branches for parallel agent work |
+| `scripts/pause.sh` / `resume.sh` / `sync.sh` | Lifecycle transitions |
+| `scripts/close-project.sh` / `close-knowledge.sh` | Close out and synthesize learnings |
+| `scripts/cancel.sh` | Cancel without merge |
+| `scripts/propose-knowledge.sh` | Standalone org knowledge proposals |
+| `scripts/onboard-repo.sh` | Bring an existing code repo under the framework |
+| `scripts/test-merge.sh` | Local pre-merge validator (used by lifecycle scripts) |
+| `scripts/validate/run.py` | Schema/registry/lifecycle/cross-ref validators |
+| `scripts/sync-from-publish.sh` | Pull universal updates from the framework's upstream branch |
+
+---
+
+## Status
+
+This framework is in active use at the upstream maintainer org and is offered as-is for other organizations to adopt. Issues and PRs are welcome — see [CONTRIBUTING.md](CONTRIBUTING.md).
+
+---
+
+## License
+
+MIT — see [LICENSE](LICENSE).
+
+Copyright (c) 2026 Svayam Infoware Private Limited and contributors.

package/agent/harness-manifest.yaml

@@ -0,0 +1,225 @@
+# Harness manifest — drives scripts/render-harness.sh
+# Canonical protocol: agent/session-protocol.md + agent.md
+# Spec: docs/design/agent-context-assembly-spec.md §3.3, Appendix C, Appendix D
+#
+# Do not hand-edit generated install paths listed under harnesses[].path when
+# generated: true. Run ./scripts/render-harness.sh after editing session-protocol.
+
+version: 1
+
+canonical:
+  session_protocol: agent/session-protocol.md
+  org_entrypoint: framework/agent.md
+  adopter_marker: "<!-- ADOPTER_C03_EXTENSIONS -->"
+
+# Delivery tiers (see spec Appendix D)
+#   import         — file expand at launch (@import); Claude Code only today
+#   generate_auto  — render-harness embeds protocol; tool auto-loads install path
+#   generate_manual— render-harness embeds protocol; developer must invoke (--read)
+#   fallback       — no repo convention; paste ./prj context assemble output
+
+tiers:
+  import:
+    description: Expand canonical files into startup context at tool launch
+  generate_auto:
+    description: Generated install path auto-loaded by the tool
+  generate_manual:
+    description: Generated file exists but developer must pass a flag or slash-command
+  fallback:
+    description: No install path; use kickoff prompt + transcript reads
+
+generated_banner: "<!-- GENERATED FROM agent/session-protocol.md — do not edit; run ./scripts/render-harness.sh -->"
+
+harnesses:
+  # ── Tier: import ──────────────────────────────────────────────────────────
+  - id: claude-code
+    tool: Claude Code
+    status: active
+    tier: import
+    path: framework/CLAUDE.md
+    generated: false
+    seed_copy: true
+    per_project_path: projects/{project_id}/CLAUDE.md
+    per_project_template: |
+      @../../agent/session-protocol.md
+      @agent.md
+
+      <!-- ADOPTER_C03_EXTENSIONS -->
+    verify: "Run /memory — must list CLAUDE.md and imported agent files"
+    notes: |
+      Claude does not read AGENTS.md unless @AGENTS.md is added.
+      First @import shows approval dialog once per project.
+
+  # ── Tier: generate_auto ───────────────────────────────────────────────────
+  - id: cursor
+    tool: Cursor
+    status: active
+    tier: generate_auto
+    path: framework/.cursor/rules/agent.mdc
+    generated: true
+    seed_copy: true
+    template: cursor-mdc
+    template_extra:
+      description: "Agentic Development Framework — session-start protocol (POL-113..117)"
+      globs: '["**/*"]'
+      alwaysApply: true
+    verify: "Cursor Settings → Rules — agent.mdc must show Always"
+    notes: |
+      Injected on every Chat/Agent/Composer turn when alwaysApply is true.
+      Inline Edit (Cmd+K) may not receive full rules.
+
+  - id: openai-codex
+    tool: OpenAI Codex
+    status: active
+    tier: generate_auto
+    path: framework/AGENTS.md
+    generated: true
+    seed_copy: true
+    template: markdown-plain
+    verify: "First message — ask agent to summarize session protocol"
+    notes: "Plain markdown; Codex CLI, Codex Web, ChatGPT coding mode."
+
+  - id: gemini-code-assist
+    tool: Gemini Code Assist
+    status: active
+    tier: generate_auto
+    path: framework/.gemini/styleguide.md
+    generated: true
+    seed_copy: true
+    template: markdown-plain
+    verify: "First message — ask what styleguide/rules were loaded"
+    notes: |
+      Convention name is styleguide; content is session protocol.
+      Re-check Google docs when extension updates.
+
+  - id: github-copilot
+    tool: GitHub Copilot
+    status: active
+    tier: generate_auto
+    path: framework/.github/copilot-instructions.md
+    generated: true
+    seed_copy: true
+    template: markdown-plain
+    verify: "Copilot assist on a repo file — ask it to state write restrictions"
+    notes: |
+      Edit-time assist, not a full agent session. Weaker C01 gate than Cursor/Claude.
+      Same folder holds GitHub Actions — do not mix CI config into instructions.
+
+  - id: windsurf
+    tool: Windsurf
+    status: active
+    tier: generate_auto
+    path: framework/.windsurf/rules/agent.md
+    generated: true
+    seed_copy: true
+    template: markdown-plain
+    verify: "First message — confirm rules loaded"
+
+  - id: cline
+    tool: Cline / Roo Code
+    status: active
+    tier: generate_auto
+    path: framework/.clinerules/agent.md
+    generated: true
+    seed_copy: true
+    template: markdown-plain
+    verify: "Open projects/{project_id}/ as workspace; confirm rules on startup"
+    notes: "Supports nested .clinerules/ per subdirectory."
+
+  - id: continue
+    tool: Continue.dev
+    status: active
+    tier: generate_auto
+    path: framework/.continue/rules.md
+    generated: true
+    seed_copy: true
+    template: markdown-plain
+    verify: "First message — confirm system rules loaded"
+    notes: "Complements .continue/config.yaml context providers."
+
+  # ── Tier: generate_manual ─────────────────────────────────────────────────
+  - id: aider
+    tool: Aider
+    status: active
+    tier: generate_manual
+    path: framework/CONVENTIONS.md
+    generated: true
+    seed_copy: true
+    template: markdown-plain
+    invoke: "aider --read CONVENTIONS.md …"
+    verify: "Confirm CONVENTIONS.md in aider context at session start"
+
+  # ── Tier: fallback (registered, not generated) ────────────────────────────
+  - id: chatgpt-web
+    tool: ChatGPT (web) / custom GPT
+    status: registered
+    tier: fallback
+    path: null
+    verify: "Paste kickoff prompt from DEVELOPER_GUIDE §3"
+    notes: "No repo-local auto-load."
+
+  - id: jetbrains-ai
+    tool: JetBrains AI Assistant
+    status: planned
+    tier: generate_auto
+    path: .junie/guidelines.md
+    generated: true
+    seed_copy: false
+    template: markdown-plain
+    notes: "Verify path against JetBrains docs before enabling."
+
+  - id: amazon-q
+    tool: Amazon Q Developer
+    status: planned
+    tier: generate_auto
+    path: .amazonq/rules.md
+    generated: true
+    seed_copy: false
+    template: markdown-plain
+    notes: "Path TBD — confirm with AWS docs before enabling."
+
+  - id: sourcegraph-cody
+    tool: Sourcegraph Cody
+    status: planned
+    tier: generate_auto
+    path: .sourcegraph/cody-rules.md
+    generated: true
+    seed_copy: false
+    template: markdown-plain
+    notes: "Path TBD."
+
+# Templates (consumed by render-harness.sh)
+templates:
+  cursor-mdc: |
+    ---
+    description: {{template_extra.description}}
+    globs: {{template_extra.globs}}
+    alwaysApply: {{template_extra.alwaysApply}}
+    ---
+
+    {{render.generated_banner}}
+
+    {{render.body}}
+  markdown-plain: |
+    {{render.generated_banner}}
+
+    {{render.body}}
+  claude-import-stub: |
+    @agent/session-protocol.md
+    @agent.md
+
+    <!-- ADOPTER_C03_EXTENSIONS -->
+
+# Per-project composition (seed / render-harness --project)
+per_project:
+  compose_body: |
+    {{render.session_protocol_body}}
+
+    ---
+
+    # Project entrypoint
+
+    @agent.md
+  note: |
+    For Cursor/Aider/etc., render-harness concatenates session-protocol + projects/PID/agent.md
+    into the generated install path. For Claude, per_project_template uses separate @imports.

package/agent/session-protocol.md

@@ -0,0 +1,116 @@
+# Agent Session-Start Protocol — <ORG_NAME>
+
+This is the **canonical** session-start protocol for any AI coding agent working in this workspace. It is delivered to each tool at its conventional path (`CLAUDE.md`, `.cursor/rules/agent.mdc`, `AGENTS.md`, `CONVENTIONS.md`, …) by `scripts/render-harness.sh`, driven by `agent/harness-manifest.yaml`. **Edit the protocol here, then re-render — never hand-edit the generated copies** (they carry a "do not edit" banner).
+
+## 0. New session — agent speaks first (Pattern 1)
+
+**Applies to:** every new Cursor Agent/Chat session, every new `claude` invocation, and every new conversation after `/clear`.
+
+When this protocol is loaded, your **first assistant message** in the session must run the C01 checklist (§1–§2 below) and post a **context manifest** — **before** planning work, proposing tasks, or editing files.
+
+| Trigger | What you do |
+|---|---|
+| User's first message is a greeting, "start", "go", "ready", or session opener | Run §1–§2, post manifest, **stop and wait** |
+| User's first message already contains a **specific work task** | Still run §1–§2 first; post a **short** manifest, then address the task |
+| No active project (framework/contrib mode; no `active` entry in `registry.yaml`) | Post manifest stating no active project; load org layer + `agent.md` only; wait for direction |
+
+**Do not** wait for the user to paste the kickoff prompt from `DEVELOPER_GUIDE.md` — that template is for humans; you execute the same steps proactively.
+
+### Context manifest (required format)
+
+Use this structure in your first reply:
+
+```markdown
+## Context manifest
+
+- **Project:** <PROJECT_ID or "none">
+- **Branch:** <current git branch>
+- **Status / assigned_to:** <from project.yaml, or n/a>
+- **Repos:** <primary repos from project.yaml, or n/a>
+- **Open todos:** <bullets from todo.md ## Open, or "none">
+- **Layers loaded:** org ✓/✗ · project ✓/✗ · repo ✓/✗ · prefs ✓/✗
+- **Awaiting:** your direction (no tasks proposed)
+```
+
+After the manifest, **stop**. Do not propose implementation work unless the user's first message already asked for something specific — and even then, complete the manifest first.
+
+---
+
+Before you change any code, complete the steps below.
+
+## 1. Read `org-config.yaml` first — every framework file references its values
+
+Read `org-config.yaml` at the workspace repo root before anything else. The framework ships with no org-specific values baked in; instead, files refer to org values via angle-bracketed tokens that map to keys in `org-config.yaml`:
+
+| Token | Key in `org-config.yaml` |
+| --- | --- |
+| `<ORG_NAME>` | `org_name` |
+| `<ORG_SHORT_NAME>` | `org_short_name` |
+| `<ORG_SLUG>` | `org_slug` |
+| `<org_slug>` (lowercase) | `org_slug_lower` |
+| `<ORG_REPO_URL>` | `org_repo_url` |
+| `<GITHUB_ORG>` | `github_org` |
+| `<WORKSPACE_REPO>` | `workspace_repo` |
+| `<DEFAULT_BRANCH>` | `default_branch` |
+| `<DEFAULT_CODE_BRANCH>` | `default_code_branch` |
+| `<AGENT_WORK_ROOT>` | `agent_work_root` |
+| `<POLICY_OWNER_EMAIL>` | `policy_owner_email` |
+| `<POLICY_OWNER_GITHUB>` | `policy_owner_github` |
+| `<LEGAL_OWNER_GITHUB>` etc. | `legal_owner_github`, `infra_owner_github`, `system_arch_owner_github`, `data_arch_owner_github` |
+| `<POLICY_EFFECTIVE_DATE>` | `policy_effective_date` |
+
+Tokens like `<PROJECT_ID>`, `<repo-name>`, `<your-gh-login>` are per-session values you'll discover from the current branch, `registry.yaml`, and `gh api user`.
+
+If `org-config.yaml` has empty values (`org_name: ""`), the workspace is still in TEMPLATE state. Hard-stop and tell the human to run `./setup.sh`.
+
+## 2. Load four knowledge layers — fresh every session
+
+Read these in priority order (highest first). Never use cached layers from a prior session:
+
+1. **Org-wide knowledge** — `knowledge/` in this repo, from the `<DEFAULT_BRANCH>` branch.
+2. **Active project** — `projects/<PROJECT_ID>/knowledge/` plus the project's own entrypoint at `projects/<PROJECT_ID>/agent.md`. To determine the active `PROJECT_ID`: check `registry.yaml` for entries with `status: active`, and check the current git branch (project branches are named `brnch-NNN-<slug>`).
+3. **Repo-local** — `<repo>/knowledge/` for each linked code repo at `$AGENT_WORK_ROOT/<PROJECT_ID>/<repo-name>/`.
+4. **Your developer preferences** — `$AGENT_WORK_ROOT/preferences/<your-gh-login>.md`. Run `gh api user --jq .login` to determine your handle; load **only** your file. Other files in that directory belong to other developers — do not read them.
+
+Higher layers always win. Developer preferences cannot override repo-local or org-wide knowledge.
+
+## 3. Verify project state (C01 — hard stops)
+
+If a project is active:
+
+- Confirm you are authorized: you have **write access to the project's linked GitHub Project** (the authorization source of truth — an owner grants it via `./prj manage assign`). `assigned_to` in `project.yaml` is a display/audit cache, **not** the gate. When on a task sub-branch (`brnch-NNN-<slug>/<task-slug>`), confirm that sub-branch's assignee is you.
+- `project.yaml`'s `status` must be `active`.
+- Read `projects/<PROJECT_ID>/knowledge/todo.md` and surface its `## Open` items to the developer before planning new work.
+
+If any of these can't be verified, hard-stop and surface to the human. Do not commit anything.
+
+## 4. What's writable, what's not
+
+During an active project:
+
+- ✅ Writable: `projects/<PROJECT_ID>/` (workspace repo) and code on the project branch in cloned repos under `$AGENT_WORK_ROOT/<PROJECT_ID>/`.
+- ❌ Read-only: `<WORKSPACE_REPO>/knowledge/` — never edit during an active project.
+- ❌ Never hand-manage task state — tasks are GitHub Issues on the board (open = active, closed = done); create with `./prj task`, land with `./prj merge`.
+- ❌ Don't create GitHub Issues unilaterally — those represent business intent that humans add to the GitHub Project board.
+
+## 5. Where work happens
+
+- Code repos are cloned at `$AGENT_WORK_ROOT/<PROJECT_ID>/<repo-name>/`, each on the project branch.
+- Code changes go in those cloned repos — **NOT** in the workspace repo's tree.
+- Project metadata (knowledge, decisions, to-dos) goes in `projects/<PROJECT_ID>/` in the workspace repo.
+
+## 6. During work
+
+- Capture decisions, exceptions, and policy notes in `projects/<PROJECT_ID>/knowledge/` as you make them — not at session end.
+- **Draw, don't just describe.** When the knowledge you're capturing has a flow, architecture, sequence, state machine, or relationship, author it as a **Mermaid diagram (text, never an image — POL-414)** instead of prose. One artifact serves both readers: it renders as a picture for humans and stays ~tens of diffable, RAG-indexable lines for agents and PR review. Default to a diagram for anything structural; reach for `flowchart`/`sequenceDiagram`/`stateDiagram`/`erDiagram`/`C4Context` as fits.
+- Capture intermediate to-dos in `projects/<PROJECT_ID>/knowledge/todo.md` under `## Open` as they arise.
+- When an item from `todo.md` is resolved, move it to `## Done` with a short note (commit SHA, PR link, or one-line outcome).
+
+---
+
+For the canonical, full version of this protocol and the policy that governs it:
+
+- **`docs/DEVELOPER_GUIDE.md`** — step-by-step session walkthrough with example prompts.
+- **`knowledge/policies/agentic-development-policy.md`** — full policy text. POL-113 through POL-171 govern session protocol.
+
+Per-project specifics (the actual `<PROJECT_ID>`, paths, GitHub Project URL, etc.) are filled in at `projects/<PROJECT_ID>/agent.md` once the project is seeded — that file is your project-specific entrypoint.

package/bin/prj

@@ -0,0 +1,21 @@
+#!/usr/bin/env bash
+# @svayam/prj — npm bin wrapper for the bash CLI.
+# Resolves the workspace (the governance repo) and execs the bundled `prj`.
+# The CLI code ships in this package; org data lives in the workspace.
+set -euo pipefail
+HERE="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
+PKG="$(cd "$HERE/.." && pwd)"          # package root: <...>/node_modules/@svayam/prj
+# Discover the workspace: explicit env, else nearest ancestor with org-config.yaml.
+if [[ -z "${ADF_WORKSPACE:-}" ]]; then
+  d="$PWD"
+  while [[ "$d" != "/" ]]; do
+    if [[ -f "$d/org-config.yaml" ]]; then ADF_WORKSPACE="$d"; break; fi
+    d="$(dirname "$d")"
+  done
+fi
+if [[ -z "${ADF_WORKSPACE:-}" || ! -f "${ADF_WORKSPACE:-}/org-config.yaml" ]]; then
+  echo "prj: no workspace found here. cd into your governance repo, or set ADF_WORKSPACE." >&2
+  exit 1
+fi
+export ADF_WORKSPACE
+exec "$PKG/prj" "$@"

package/package.json

@@ -0,0 +1,41 @@
+{
+  "name": "@svayam-opensource/prj",
+  "version": "0.5.1",
+  "description": "Governed Agentic Development Framework CLI (prj). A bash CLI wrapped for npm; operates on a governance workspace resolved via $ADF_WORKSPACE or the nearest org-config.yaml. Runtime prerequisites (not npm deps): bash, git, gh, yq, python3 (use Git Bash on Windows).",
+  "bin": {
+    "prj": "bin/prj"
+  },
+  "files": [
+    "prj",
+    "bin/",
+    "setup.sh",
+    "agent/",
+    "scripts/*.sh",
+    "scripts/validate/*.py"
+  ],
+  "os": [
+    "darwin",
+    "linux",
+    "win32"
+  ],
+  "engines": {
+    "node": ">=14"
+  },
+  "preferGlobal": true,
+  "publishConfig": {
+    "registry": "https://registry.npmjs.org/",
+    "access": "public"
+  },
+  "keywords": [
+    "cli",
+    "agentic",
+    "governance",
+    "framework",
+    "prj"
+  ],
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/svayam-opensource/governed-agentic-dev-framework.git"
+  }
+}