manifests

Overview ¶

Package manifests is the dependency-manifest ingestion adapter: it parses `go.mod` and `package.json` files at the repo root plus one nested level (e.g. frontend/, backend/, landings*/) into `derived` facts.

Feature: cli/studio/index (REQ: adapter-manifests)

Emitted predicates:

• publishes — the module/package identity a manifest declares (go.mod `module` directive; package.json `name` + `version`)
• consumes — one fact per direct dependency with its version specifier (go.mod non-indirect `require` lines; package.json `dependencies` and `devDependencies`)

Subjects are emitted repo-relative (`#<manifest-path>`, e.g. `#go.mod`, `#frontend/package.json`); the pipeline prefixes them with the workspace-scoped repo slug. Objects are package IDs (`module@version`, version omitted when the manifest declares none). Dot-directories and node_modules are never scanned.