npm - create-mercato-app - Versions diffs - 0.6.8-develop.6961.1.5b7ca407e7 → 0.6.8-develop.6962.1.bd029a2bb2 - Mend

create-mercato-app 0.6.8-develop.6961.1.5b7ca407e7 → 0.6.8-develop.6962.1.bd029a2bb2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (898) hide show

package/agentic/guides/architecture.md CHANGED Viewed

@@ -11,7 +11,7 @@ The harness is intentionally layered so an agent can assemble precise context wi
 | Root `AGENTS.md` | Non-negotiable safety, validation, precedence, and the three-axis router | Load first and always; it is the only initial bundle. |
 | `.ai/guides/*.md` | Stable framework concepts and contracts by area | Load the de-duplicated set selected by the area and primitive axes. |
 | Thin task skills | Branching procedure and links to focused references | Load only matched skills; open only the references needed by the chosen branch. |
-| `.ai/guides/modules/*.md` | Generated identifiers and discovered surfaces for an exact installed module/version | Load only for installed modules named, changed, integrated with, or used as hosts. |
+| `.ai/guides/modules/<id>/` | Generated identifiers and discovered surfaces for an exact installed module/version | Start at `index.md`, then load only the sections needed for named, changed, integrated, or hosting modules. |
 | `om-framework-context` output | Exact installed instructions, source/types, and bounded search results | Last-mile escalation after app call sites, facts, and concept guides cannot answer the question. |
 | External `open-mercato/skills` | SDLC and delivery workflows | Select independently only when the requested lifecycle needs one. |
@@ -82,7 +82,7 @@ For the complete current convention-file catalog, load `om-module-scaffold` →
 ## Installed Framework Context
-1. Read `.ai/guides/modules/<id>.md` for entity IDs, events, routes/auth, ACL, DI, search, notifications, and host spots.
+1. Read `.ai/guides/modules/<id>/index.md` for the section inventory, then open only the files covering the required entity IDs, events, routes/auth, ACL, DI, search, notifications, or host spots. Every generated index and section ends with a marker; if a capped read does not reach it, re-read the missing content from the index rather than assuming the read was complete.
 2. When facts are insufficient, invoke `om-framework-context` or run `yarn framework:context --module <id> --query <term>`.
 3. Confirm the resolved package/version matches the fact sheet stamp.
 4. Read the reported instruction chain in precedence order, then search only the reported package/module root with the bounded `rg --no-ignore --hidden` command.

package/agentic/guides/extensions.md CHANGED Viewed

@@ -7,7 +7,7 @@ Use the smallest extension mechanism that preserves installed-module ownership.
 Resolve an installed extension in this order:
 1. Choose the mechanism by intent below; the mechanism decides which contribution kind and host capability are required.
-2. Open only the named target module sheet at `.ai/guides/modules/<module>.md`. Its `UMES hosts` rows prove mountable exact/pattern targets; its `UMES contributions` rows preserve activation, phases/operations, feature and scope contracts, specialist routes, correlation resolution, and read/write/UI `roundTripId` links.
+2. Open only the named target module sheet at `.ai/guides/modules/<module>/index.md`. Its `UMES hosts` rows prove mountable exact/pattern targets; its `UMES contributions` rows preserve activation, phases/operations, feature and scope contracts, specialist routes, correlation resolution, and read/write/UI `roundTripId` links.
 3. For global shell, menu, dashboard, notification, or integration surfaces, use `.ai/guides/framework-extension-points.md`. Do not assign a framework-owned host to a business module or invent a `$framework` module.
 4. Follow a contribution's `fact-ref` or `specialistRoute` to the existing event/entity/API/command/search/AI/provider facts and owning specialist route. A specialized registry is not evidence for a generic widget target.
 5. Use `om-framework-context` for one named unresolved installed-version gap only. An `optional-external` target is explicit provenance and must degrade when its owner package is absent; an `unresolved` first-party target is a blocker, not permission to guess.

package/agentic/guides/module-system.md CHANGED Viewed

@@ -12,4 +12,4 @@ Use the concern guides below. This path remains only so older prompts and links
 | AI agents/tools/orchestrators or workflows | `.ai/guides/ai-workflows.md` |
 | Diagnosis and regression verification | `.ai/guides/testing-debugging.md` |
-For a complete new module, invoke `om-module-scaffold`; it loads the relevant branches. For a concrete installed-module fact, read its generated `.ai/guides/modules/<id>.md` first. Invoke `om-framework-context` only when generated facts cannot answer the implementation question.
+For a complete new module, invoke `om-module-scaffold`; it loads the relevant branches. For a concrete installed-module fact, read its generated `.ai/guides/modules/<id>/index.md` first. Invoke `om-framework-context` only when generated facts cannot answer the implementation question.