In examples/basic-rest/open-api.json around lines 10 to 17 (and similarly at
171-177 and 331-337), the path parameter "id" is declared as a string while the
DTOs use numeric ids; update the "schema" for these path parameters to use type
"integer" (or "number" if decimals are expected) and add "format": "int64" (or
"int32" as appropriate) to match the DTOs, ensuring required remains true and
validation will accept numeric ids for sub-task, todo-item, and tag endpoints.

In examples/basic-rest/open-api.json around lines 393 to 401, the PUT
requestBody currently references CreateTagDTO which is incorrect for updates;
add a new components/schemas/TagUpdateDTO with the same properties as
CreateTagDTO but make fields optional (e.g., name optional) and replace the
requestBody schema $ref to "#/components/schemas/TagUpdateDTO"; ensure the new
schema is added under components.schemas and referenced by the PUT operation.

In examples/basic-rest/src/sub-task/dto/sub-task.dto.ts around lines 22 to 23,
the todoItemId property is declared as a string but should be a number to match
TodoItemEntity.id and other DTOs; change the property type from string to number
(and adjust any decorators or validators if they assume string) so the DTO's
todoItemId uses number throughout the REST surface to remain consistent with the
entity.

In examples/basic-rest/src/sub-task/dto/subtask-input.dto.ts around lines 20 to
22, the todoItemId is declared as a string but the entity TodoItemEntity.id is
numeric; change the DTO to accept a numeric id and validate/transform it by
making the property a number, adding class-validator checks (e.g., @IsInt or
@IsNumber) and using class-transformer's @Type(() => Number) to coerce incoming
values to number (ensure the validation pipe is enabled so non-numeric input is
rejected).

In examples/basic-rest/src/tag/tag.entity.ts around lines 19 to 20, the
@ManyToMany decorator is using an incorrect ObjectType<TodoItemEntity> wrapper;
change it to pass the entity class directly by replacing the first argument with
a function that returns the entity class (i.e. () => TodoItemEntity) and keep
the inverse side (td => td.tags); ensure TodoItemEntity is imported so the
decorator reads like @ManyToMany(() => TodoItemEntity, td => td.tags) and
nothing else needs to change.

In packages/query-rest/src/types/query/paging/interfaces.ts around lines 5 to
14, the two paging aliases are identical which removes type discrimination; make
each alias a lightweight branded/nominal type so the union preserves
distinction. Replace NonePagingType and OffsetPagingType with intersections that
add a unique phantom property or symbol (e.g. Paging & { __pagingKind: 'none' }
and Paging & { __pagingKind: 'offset' }) and update PagingTypes and
InferPagingTypeFromStrategy to use those branded types so conditional types
correctly discriminate on PagingStrategies.

In packages/query-rest/src/types/query/query-args/constants.ts around lines 1 to
6, the exported DEFAULT_QUERY_OPTS contains mutable defaults (defaultSort: []
and defaultFilter: {}) that can be mutated across requests; replace these with
frozen values and freeze the container to prevent accidental mutation (e.g. use
Object.freeze([]) for defaultSort, Object.freeze({}) for defaultFilter and
Object.freeze(...) on the DEFAULT_QUERY_OPTS object so none of its properties
can be altered at runtime).

In packages/query-rest/tsconfig.lib.json around lines 3 to 10, the
compilerOptions block is missing "composite": true which is required for project
references; update the file by adding "composite": true to the compilerOptions
object so this project can be referenced and built with tsc -b (ensure the JSON
remains valid and commas are adjusted as needed).