BOLT-1322 [3/7] domains/device: Prisma + GraphQL — add Command.output JSON column

Add Command.output to Prisma schema + GraphQL Command type + mappers. 1. domains/device/prisma/schema.prisma: add 'output Json?' to the Command model. Generate migration: 'pnpm prisma migrate dev --name add_output_to_command --schema domains/device/prisma/schema.prisma' (or whatever the repo's convention is — check Makefile / package.json scripts). 2. domains/device/src/repositories/commandRepository/types.ts (or equivalent): include output in CreateCommandInput / UpdateCommandInput / Command DAO type. 3. domains/device/src/subgraph/schema/types/command/index.ts: add 'output: JSON' to the Command typeDef. Add output to the mapper at the top of the file (the spread already in the mapper). 4. domains/device/src/services/command/mappers.ts: include output in mapCommandDao. 5. Regenerate subgraph.lock.graphql via the repo's script (likely 'pnpm build:subgraph' or similar — check package.json). 6. Add unit test for the mapper output field. 7. Verify schema federation/composition still passes locally. Branch: havoc/bolt-1322-prisma-graphql Worktree: ../mono-bolt-1322-prisma-graphql Depends on: ideally land after [1/7] and [2/7] so types compile coherently, but Prisma schema work can start in parallel. Done when: migration runs cleanly against fresh + existing DBs, GraphQL Command.output is queryable, mappers pass through output correctly.