{"owner":"hatchet-dev","repo":"hatchet","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md"],"skills":{"AGENTS.md":"# AGENTS\n\n## CI\n\n- Any CI surface that boots a Hatchet server instance (engine, API, `hatchet-lite`, docker-compose, or helm) must set `SERVER_SECURITY_CHECK_ENABLED=false`. The check defaults to enabled and phones home to `security.hatchet.run`; CI must never do that. `go test`-based boots are already covered by the test harness; every other boot site sets the var explicitly.\n\n## Code Comments\n\n- Comments should explain non-obvious intent, invariants, or constraints in the current code. Do not mention the old implementation/state (for example, \"preserve the behavior of the original query\"); state the current rule directly.\n\n## Tests\n\n- Do not include customer names, tenant names, or production namespace names in test names, fixtures, comments, or logs. Describe the scenario by structural properties instead (for example, `dense_high_action_fanout`, not a customer or shard name).\n\n## Docs MDX\n\n- In MDX JSX component bodies, such as ``, avoid Markdown link syntax (`[text](href)`). Prettier can wrap the label across lines and break MDX parsing. Use an explicit JSX link instead:\n\n```mdx\n\n See the{\" \"}\n \n Go SDK client retry behavior section\n \n\n```\n"},"files":{"AGENTS.md":"# AGENTS\n\n## CI\n\n- Any CI surface that boots a Hatchet server instance (engine, API, `hatchet-lite`, docker-compose, or helm) must set `SERVER_SECURITY_CHECK_ENABLED=false`. The check defaults to enabled and phones home to `security.hatchet.run`; CI must never do that. `go test`-based boots are already covered by the test harness; every other boot site sets the var explicitly.\n\n## Code Comments\n\n- Comments should explain non-obvious intent, invariants, or constraints in the current code. Do not mention the old implementation/state (for example, \"preserve the behavior of the original query\"); state the current rule directly.\n\n## Tests\n\n- Do not include customer names, tenant names, or production namespace names in test names, fixtures, comments, or logs. Describe the scenario by structural properties instead (for example, `dense_high_action_fanout`, not a customer or shard name).\n\n## Docs MDX\n\n- In MDX JSX component bodies, such as ``, avoid Markdown link syntax (`[text](href)`). Prettier can wrap the label across lines and break MDX parsing. Use an explicit JSX link instead:\n\n```mdx\n\n See the{\" \"}\n \n Go SDK client retry behavior section\n \n\n```\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","title":"AGENTS.md","content":"# AGENTS\n\n## CI\n\n- Any CI surface that boots a Hatchet server instance (engine, API, `hatchet-lite`, docker-compose, or helm) must set `SERVER_SECURITY_CHECK_ENABLED=false`. The check defaults to enabled and phones home to `security.hatchet.run`; CI must never do that. `go test`-based boots are already covered by the test harness; every other boot site sets the var explicitly.\n\n## Code Comments\n\n- Comments should explain non-obvious intent, invariants, or constraints in the current code. Do not mention the old implementation/state (for example, \"preserve the behavior of the original query\"); state the current rule directly.\n\n## Tests\n\n- Do not include customer names, tenant names, or production namespace names in test names, fixtures, comments, or logs. Describe the scenario by structural properties instead (for example, `dense_high_action_fanout`, not a customer or shard name).\n\n## Docs MDX\n\n- In MDX JSX component bodies, such as ``, avoid Markdown link syntax (`[text](href)`). Prettier can wrap the label across lines and break MDX parsing. Use an explicit JSX link instead:\n\n```mdx\n\n See the{\" \"}\n \n Go SDK client retry behavior section\n \n\n```\n","category":"root","tokens":318}]}