# toolregistry-hub - Doramagic AI Context Pack > Purpose: pre-work context for the user's host AI. This pack does not prove that the project has been installed, run, or validated. ## Project - canonical_name: `Oaklight/toolregistry-hub` - capability: ToolRegistry Hub: Ready-to-Use Tool Collection for LLM Agents — web search, file ops, code execution, and more - expected_user_outcome: ToolRegistry Hub: Ready-to-Use Tool Collection for LLM Agents — web search, file ops, code execution, and more ## Operating Boundaries - Do not claim that the project has been installed, run, called through an API, or used on local files unless separate evidence proves it. - Project facts must come from repo evidence, Claim Graph, or explicit source references. - When a capability is not verified, mark it as unverified instead of completing it as fact. - publish_status: `publishable` - blocking_gaps: none --- ## Doramagic Context Augmentation The following sections strengthen the repository context for a host AI. Human Manual data is a reading route, and pitfall notes become operating constraints. ## Human Manual Outline Usage rule: this is only a reading route and salience signal, not factual authority. Concrete claims must still return to repo evidence or Claim Graph. Host AI hard rules: - Do not treat page titles, section order, summaries, or importance values as factual project evidence. - When explaining the Human Manual outline, state that it is only a reading route or salience signal. - Capability, installation, compatibility, runtime state, and risk claims must cite repo evidence, source paths, or Claim Graph. - **Overview and Architecture**: importance `high` - source_paths: README.md, src/toolregistry_hub/__init__.py, src/toolregistry_hub/server/app.py, src/toolregistry_hub/server/registry.py, pyproject.toml - **Core Tools Library**: importance `high` - source_paths: src/toolregistry_hub/calculator.py, src/toolregistry_hub/datetime_utils.py, src/toolregistry_hub/file_ops.py, src/toolregistry_hub/file_reader.py, src/toolregistry_hub/file_search.py - **Server, CLI, and Configuration**: importance `high` - source_paths: src/toolregistry_hub/server/app.py, src/toolregistry_hub/server/cli.py, src/toolregistry_hub/server/registry.py, src/toolregistry_hub/server/banner.py, src/toolregistry_hub/server/__init__.py - **Deployment, Distribution, and Operations**: importance `high` - source_paths: docker/Dockerfile, docker/compose.yaml, docker/compose.dev.yaml, docker/Caddyfile, docker/.env.sample ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `20b97a535f8a767bd648e89aa07f46f9db87558d` - inspected_files: `README.md`, `pyproject.toml`, `src/toolregistry_hub/__init__.py`, `src/toolregistry_hub/_vendor/__init__.py`, `src/toolregistry_hub/_vendor/cdp/__init__.py`, `src/toolregistry_hub/_vendor/cdp/cdp.py`, `src/toolregistry_hub/_vendor/httpclient.py`, `src/toolregistry_hub/_vendor/readability/__init__.py`, `src/toolregistry_hub/_vendor/readability/readability.py`, `src/toolregistry_hub/_vendor/scheduler.py`, `src/toolregistry_hub/_vendor/soup/__init__.py`, `src/toolregistry_hub/_vendor/soup/soup.py`, `src/toolregistry_hub/_vendor/structlog.py`, `src/toolregistry_hub/_vendor/useragent.py`, `src/toolregistry_hub/_vendor/validate.py`, `src/toolregistry_hub/_vendor/websocket/__init__.py`, `src/toolregistry_hub/_vendor/websocket/websocket.py`, `src/toolregistry_hub/bash_tool.py`, `src/toolregistry_hub/calculator.py`, `src/toolregistry_hub/cron_tool.py` Host AI hard rules: - Without repo_clone_verified=true, do not claim that the source code has been read. - Without repo_inspection_verified=true, do not write README, docs, or package-file conclusions as facts. - Without quick_start_verified=true, do not claim that the Quick Start path has run successfully. ## Doramagic Pitfall Constraints These rules come from Doramagic discovery, validation, or compilation findings. The host AI must treat them as operating constraints, not background notes. ### Constraint 1: Capability evidence risk requires verification - Trigger: README/documentation is current enough for a first validation pass. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: capability.assumptions | https://github.com/Oaklight/toolregistry-hub - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 2: Maintenance risk requires verification - Trigger: Project evidence flags a maintenance risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/Oaklight/toolregistry-hub/issues/150 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 3: Maintenance risk requires verification - Trigger: Project evidence flags a maintenance risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: evidence.maintainer_signals | https://github.com/Oaklight/toolregistry-hub - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 4: Security or permission risk requires verification - Trigger: no_demo - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: downstream_validation.risk_items | https://github.com/Oaklight/toolregistry-hub - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 5: Security or permission risk requires verification - Trigger: no_demo - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: risks.scoring_risks | https://github.com/Oaklight/toolregistry-hub - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 6: Security or permission risk requires verification - Trigger: Project evidence flags a security or permission risk. Review the linked source before relying on this workflow. - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: community_evidence:github | https://github.com/Oaklight/toolregistry-hub/issues/148 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 7: Maintenance risk requires verification - Trigger: issue_or_pr_quality=unknown。 - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: evidence.maintainer_signals | https://github.com/Oaklight/toolregistry-hub - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it. ### Constraint 8: Maintenance risk requires verification - Trigger: release_recency=unknown。 - Host AI rule: Reproduce the official install and quickstart path in an isolated environment. - Why it matters: May increase setup, validation, or first-run risk for the user. - Evidence: evidence.maintainer_signals | https://github.com/Oaklight/toolregistry-hub - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.