Blacklight Add Agent or Artifact

Add the catalog baseline deterministically, then complete the code surfaces that require semantic decisions. Treat an "agent" as an AI coding/agentic tool supported by Blacklight, not as a Codex subagent profile.

Choose the operation

• New agent/tool: require a canonical tool id, home-relative root, and at least one config path. Use add-agent.
• New artifact: require the existing tool id, stable artifact id, family, home-relative path, path kind, priority, evidence source, and assessment coverage. Use add-artifact.
• Codex custom subagent: do not use this workflow. Project profiles belong in .codex/agents/*.toml and use the Codex custom-agent schema.

Establish evidence first

1. Confirm the path from sanitized documentation, a lab system, or existing parser behavior.
2. Never copy credential values, session content, host-identifying paths, or raw evidence into catalogs, fixtures, docs, or prompts.
3. Classify the path with the existing family vocabulary whenever possible: root, auth, config, mcp, sessions, history, workspace, rules, plugins, extensions, skills, plans, telemetry, sandbox, cache, or logs.
4. Use explicitly_assessed only when Scout targets the exact path. Use recursively_discovered for bounded descendant matching and intentionally_deferred when cataloged without collection or parsing.

Scaffold the catalogs