Lifecycle Model Hybrid Search
Run Workflow
- The wrapper uses the repository-pinned published CLI. Use
TIANGONG_LCA_CLI_DIRor--cli-dironly for an exact local dev/CI override. - Official Production needs no environment setup: the CLI owns its public profile. Only Dev/self-hosted/custom clients need the complete matching configuration in
references/env.md. - Run
tiangong-lca auth status --json. If it returnslogin-required, stop and ask the human user to runtiangong-lca auth loginin a trusted terminal. - Execute
node scripts/run-lifecyclemodel-hybrid-search.mjswith standardtiangong-lca search lifecyclemodelflags. - The wrapper delegates to
tiangong-lca search lifecyclemodel; the CLI resolves and refreshes its private OAuth session. - Confirm response shape, then debug with focused references.
Never ask an AI user for a username, password, authorization code, access token, refresh token, or the deprecated encoded API key. Headless runs require an explicit destination/publishable key and may use only an orchestrator-injected short-lived TIANGONG_LCA_ACCESS_TOKEN; do not pass it through argv, prompts, logs, or artifacts.
Commands
pnpm dlx --package=@tiangong-lca/cli@0.1.18 tiangong-lca auth status --json
# Only the human user completes browser login when login-required is reported
pnpm dlx --package=@tiangong-lca/cli@0.1.18 tiangong-lca auth login
node scripts/run-lifecyclemodel-hybrid-search.mjs --dry-run
node scripts/run-lifecyclemodel-hybrid-search.mjs --input ./assets/example-request.json
# Explicit local CLI override for development only
node scripts/run-lifecyclemodel-hybrid-search.mjs --cli-dir /path/to/tiangong-lca-cli --dry-run
Fast Triage
- An independently installed skill includes its launcher and example input; no Skills/CLI/Data Foundry checkout is required. The launcher is a byte-checked bundle of the repository authority, not a separate auth implementation.
- Fresh
auth status/doctor-authreturnslogin-required(exit 1), not a missing Production client. A custom--base-urlrequires matching complete custom configuration. 400: missing or invalidquery.500: embedding provider orhybrid_search_lifecyclemodelsRPC failure.- Empty
data: query/filter mismatch; inspect generated retrieval query and filter structure.
Load References On Demand
references/env.md: auth, region, and endpoint overrides.references/request-response.md: payload contract and RPC expectations.references/prompts.md: query-rewrite prompt constraints.references/testing.md: smoke test checklist.