@rudderhq/agent-runtime-gemini-local 0.7.18 → 0.7.19-canary.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rudderhq/agent-runtime-gemini-local",
-  "version": "0.7.18",
+  "version": "0.7.19-canary.0",
   "license": "SEE LICENSE IN LICENSE",
   "homepage": "https://github.com/Undertone0809/rudder",
   "bugs": {
@@ -67,7 +67,7 @@
     "typecheck": "tsc --noEmit"
   },
   "dependencies": {
-    "@rudderhq/agent-runtime-utils": "0.7.18",
+    "@rudderhq/agent-runtime-utils": "0.7.19-canary.0",
     "picocolors": "^1.1.1"
   },
   "devDependencies": {

package/skills/rudder-docs/SKILL.md

@@ -14,7 +14,7 @@ If this body is already present in the prompt but the current request does not n
 
 Classify the Rudder question, consult the smallest authoritative source set,
 and answer with clear provenance. Use current evidence instead of memory for
-commands, interfaces, versioned behavior, and product contracts.
+commands, interfaces, versioned behavior, and design proposals.
 
 This router does not make an ordinary hosted task into a Rudder workflow. It
 does not provide a command catalog, replace runtime-owned execution rails, or
@@ -71,8 +71,8 @@ exact page. Do not crawl or load the whole site for a narrow question.
 ### Local Rudder Checkout
 
 Follow the checkout's `AGENTS.md`, then use `doc/README.md` to choose the
-documentation layer: `docs/` for public user guidance, `doc/product/` for the
-intended product contract, `doc/engineering/` for contributor detail, and
+documentation layer: `docs/` for public user guidance, `doc/plans/` for design
+proposals, `doc/engineering/` for contributor detail, and
 source and tests for exact implementation. Search the owning area narrowly and
 cite local paths and line numbers when supported.
 
@@ -92,7 +92,7 @@ limits. Missing evidence narrows the answer; it does not justify invention.
 ## Resolve Versions And Conflicts
 
 Current callable or installed behavior wins for this environment.
-`doc/product/` owns intended product semantics. Source and tests own exact implementation evidence. Public docs own published user guidance. An official
+Proposals record intended changes and rationale. Source and tests own exact implementation evidence. Public docs own published user guidance. An official
 release or tag owns version-specific history.
 
 Do not flatten disagreement:
@@ -101,10 +101,10 @@ Do not flatten disagreement:
   documentation drift;
 - installed help versus a bundled reference: use installed help here and label
   the reference version-adjacent or stale;
-- public docs versus product contract: distinguish published guidance from
-  intended semantics;
-- product contract versus source or tests: report apparent implementation
-  drift and identify both;
+- public docs versus source or tests: report documentation drift and identify
+  both;
+- proposal versus implementation: distinguish intended changes from shipped
+  behavior;
 - default branch versus installed release: use the matching release tag for
   installed behavior;
 - verified evidence versus model memory: discard unsupported memory.
@@ -115,7 +115,7 @@ together or imply certainty that the evidence does not support.
 ## Evidence And Citations
 
 - Attribute each material claim as current-environment behavior, public
-  guidance, intended contract, implementation evidence, version history, or
+  guidance, proposed design, implementation evidence, version history, or
   inference.
 - Cite or link the exact source near the claim when the host supports links.
   For local files, include the path and a tight line reference when possible.
@@ -142,7 +142,7 @@ Read only the reference needed for the request:
 6. [Organization skills](references/organization-skills.md) — discover,
    import, inspect, enable, and synchronize organization or agent skills.
 7. [Source map](references/source-map.md) — stable official documentation,
-   Product Logic, engineering, implementation, test, release, and search
+   proposal, engineering, implementation, test, release, and search
    routes.
 
 ## Security And Bounded Use
@@ -157,8 +157,8 @@ Read only the reference needed for the request:
   releases and tags. Follow stricter host policy when it applies.
 - Preserve organization and workspace boundaries. Do not use documentation
   lookup to expose private resources or cross organization scope.
-- Reading `doc/product/` is allowed for evidence; it does not authorize edits.
-  Product Logic changes require the repository's separate explicit approval.
+- Code and tests establish current behavior. Proposals record design decisions;
+  the retired `doc/product/` registry is historical reference, not an approval gate.
 - A docs-only question does not authorize mutations. If the user also asks for
   an action, apply the normal authorization and safety rules to that action.
 

package/skills/rudder-docs/references/source-map.md

@@ -7,7 +7,7 @@ directories rather than an exhaustive page list. Follow the current checkout's
 ## Section Map
 
 - [Official public documentation](#official-public-documentation)
-- [Product Logic Registry](#product-logic-registry)
+- [Design proposals](#design-proposals)
 - [Contributor and engineering documentation](#contributor-and-engineering-documentation)
 - [Implementation and tests](#implementation-and-tests)
 - [Official remote source and version history](#official-remote-source-and-version-history)
@@ -51,36 +51,12 @@ Other lookup pages are similarly narrow:
 | Windows Desktop release signing policy | `https://docs.rudderhq.dev/reference/code-signing-policy` | `https://docs.rudderhq.dev/zh/reference/code-signing-policy` |
 | Local data and optional service privacy | `https://docs.rudderhq.dev/reference/privacy` | `https://docs.rudderhq.dev/zh/reference/privacy` |
 
-## Product Logic Registry
-
-- Entry point: `doc/product/README.md`
-- Registry map: `doc/product/registry.yml`
-- Domain contracts: `doc/product/domains/`
-- Composed workflows: `doc/product/workflows/`
-- Surface-to-contract maps: `doc/product/surfaces/`
-
-Use Product Logic for intended product semantics and invariants. Start at the
-registry entry point and select the owning domain rather than scanning all
-contracts. Reading these guarded files does not authorize editing them.
-
-Common domain routes include:
-
-- agents, skills, and inbox: `doc/product/domains/agents/`
-- issues and issue-visible state: `doc/product/domains/issues/`
-- assignment, checkout, review routing: `doc/product/domains/work-routing/`
-- runs, execution, transcripts, workspaces: `doc/product/domains/execution/`
-- organizations, goals, and projects:
-  `doc/product/domains/organizations-and-goals/`
-- Library, resources, and runtime context:
-  `doc/product/domains/library-and-context/`
-- Chat, Messenger, comments, and integrations:
-  `doc/product/domains/collaboration/`
-- approvals, budgets, costs, and activity:
-  `doc/product/domains/governance-and-visibility/`
-- reviews, feedback, and learning:
-  `doc/product/domains/review-feedback-learning/`
-- automations: `doc/product/domains/automations/`
-- plugins: `doc/product/domains/plugins/`
+## Design Proposals
+
+Use `doc/plans/` for proposed designs and decision history. Verify current
+behavior against implementation and tests; a proposal is not evidence that a
+feature shipped. The old `doc/product/` registry, domains, workflows, and surface
+maps are historical reference only. They require no synchronization or approval.
 
 ## Contributor And Engineering Documentation