mirror of
https://github.com/hanzoai/insights.git
synced 2026-11-02 14:32:45 +00:00
zeekay
1b367e2b62
The tree was a debranded snapshot of upstream taken around 2026-02-20, and upstream has moved about five months since. This replaces it with upstream master, mechanically re-derived: bin/debrand does the rename, and the pipeline and squashed migrations are restored from the shipped tree. Not a merge. The previous import replaced the tree wholesale in a single commit, so there is no shared content history to merge against. Reproducing the rename on the new tree is what actually converges. What survives: .hanzo/workflows, the Dockerfiles and bin/docker* entrypoints, compose files, LLM.md, and insights/migrations. The squashed initial migration is load-bearing — the live database records it by name, so upstream's ~918 individual migrations cannot come back. Nine products are dropped as unreferenced. Twenty-one more that we do not run are kept anyway because the core app still imports them; unpicking those is a refactor and does not belong in a rebase. This base does not build yet, and the reasons are not in the rename: upstream now wants Python 3.13.13 against our 3.12.12 and Django 5.2 against our 4.2, and the dependency manifests still name upstream packages that we republish under our own names. Those are decisions, not renames.
35 lines
1.6 KiB
YAML
35 lines
1.6 KiB
YAML
rules:
|
|
- id: prefer-codegen-api
|
|
message: >-
|
|
Manual `api.<verb>(...)` call in product frontend code. Prefer the generated
|
|
client in `products/<product>/frontend/generated/api.ts`.
|
|
|
|
Agents: invoke the `adopting-generated-api-types` skill
|
|
(`.agents/skills/adopting-generated-api-types/SKILL.md`) for the migration
|
|
workflow. Humans: run `insightscli product:maturity --codegen <product>` to see
|
|
the suggested generated function per call site.
|
|
|
|
If no generated equivalent is available yet (endpoint missing OpenAPI tags,
|
|
dynamic URL, etc.), add `// nosemgrep: prefer-codegen-api` above this line —
|
|
the maturity tooling continues to track tagged sites.
|
|
severity: ERROR
|
|
languages: [typescript, javascript]
|
|
pattern-either:
|
|
- pattern: api.get(...)
|
|
- pattern: api.post(...)
|
|
- pattern: api.put(...)
|
|
- pattern: api.patch(...)
|
|
- pattern: api.delete(...)
|
|
- pattern: api.create(...)
|
|
- pattern: api.update(...)
|
|
# Semgrep's TypeScript parser treats generic-typed calls (api.create<T>())
|
|
# as a different AST shape that AST-level patterns above don't match,
|
|
# so fall back to a regex. Bounds the type args by `(` rather than `>` so
|
|
# nested generics like api.get<PaginatedResponse<Foo>>(...) still match.
|
|
- pattern-regex: '\bapi\.(get|post|put|patch|delete|create|update)<[^(]*>\s*\('
|
|
paths:
|
|
include:
|
|
- '/products/*/frontend/'
|
|
exclude:
|
|
- '**/generated/**'
|