Sub-entity (child) generator

You are helping generate a JSON schema file for a codegen CLI that uses Hygen templates. Follow the instructions precisely and do not add extra explanations or UI formatting. Output a JSON file only in the structure described below.

---

### INPUT

I will provide one of the following:
- A raw SQL `CREATE TABLE` statement for a child entity and its parent name
- A natural language description of the child entity, its parent, and its fields

You will extract the schema and create a JSON object matching the exact structure below. Skip the fields id, created_at, and updated_at as they will be added automatically.

Ensure both `parent` and `name` are PascalCase (capitalize each word, no underscores/spaces). For example, tempuser becomes TempUser, product_order becomes ProductOrder.

Then save the file at the given location and remind me of the correct CLI command to run.

---

### OUTPUT FORMAT

{
  "parent": "ParentEntityName",
  "name": "ChildEntityName",
  "functionalities": ["create", "findAll", "findAllWithSearch", "findOne", "update", "delete"],
  "fields": [
    {
      "name": "field_name",
      "type": "int | float | double | decimal | boolean | varchar | text | uuid | timestamp | date | json | custom",
      "optional": true,
      "customType": "CustomTypeName (optional if type is 'custom')",
      "example": "example_value",
      "dto": true,
      "unique": true
    }
  ]
}

> Notes:
> - `parent`: PascalCase (e.g. `User`)
> - `name`: PascalCase (e.g. `Address`)
> - `functionalities`: Array of strings. You can include either `"findAll"` or `"findAllWithSearch"` (or both, but `findAllWithSearch` will be preferred and `findAll` will be removed automatically)
> - `fields[].name`: snake_case
> - `type`: must be one of the allowed values
> - `optional`: true if nullable or optional
> - `example`: valid example for the field
> - `dto`: true if it should be included in DTOs
> - `unique`: optional boolean, set to `true` to add a unique constraint to the database column

---

### FILE OUTPUT

Once you've built the correct JSON, **save the file to this path relative to the project root**:

.hygen-entities-generator/<sub-entity-name-kebab-case>.json

Example:
.hygen-entities-generator/user-address.json

Samples for reference are available under `.hygen-sample-files/`, e.g. `sample-sub-entity-generator.json`.

---

### FINAL INSTRUCTION

Once the file is saved, tell me:

✅ Schema file generated successfully.

Now run:
DATA_FILE=.hygen-entities-generator/<sub-entity-name-kebab-case>.json npm run generate:sub-entity

---

### NOW GO AHEAD

Here is my input:

[Paste your SQL CREATE TABLE statement or natural language description here]