Make generic FLUJO teams the default SDK template with CRUD

[flujo-app]

FACTORY previously exposed a native team builder but no reusable template catalog. This change makes the generic FLUJO team the default for model-only workspace provisioning and exposes durable template list/create/read/update/delete/build through the public SDK, CLI and MCP server.

The generic team reuses the existing native agent/team flow pair and aggregate subflow gate. It attaches observed connected MCP capabilities, carries project-provided goal/environment context, and emphasizes upstream reuse, useful delivery, concise board coordination and independent review. Calma-specific goals, pins, hardware settings and recorded runs stay outside FACTORY.

Template overrides persist in the existing local database with revision checks across reset/delete/recreate. The built-in generic template remains available; deleting its override resets it. Credential fields reject before prompt/workspace mutation. CRUD and specification building do not start workers or provision paid resources.

Validation: clean tracked source feecc51. Local Windows and Linux lanes on exact Node 22.17.0 and 24.19.0 run npm ci, npm audit --omit=dev --audit-level=high, the public-sdk workflow tests plus template/catalog/workspace tests, npm pack, fresh consumer install, installed SDK/swarm/template smoke, both CLI helps and installed MCP stdio smoke. All four lanes passed 89/89 focused tests and 1/1 installed MCP smoke, with zero production audit vulnerabilities. Windows npm was 10.9.2 on both Node versions; Linux npm was 10.9.2 / 11.17.0 respectively. Linux clean installs used npm ci --offline with the host integrity cache after Docker registry timeouts; production audits ran online with host networking. A temporary Windows runner path error was corrected and only the unrun tail steps were resumed. Independent review covers the SDK/catalog/builder/adapter/CLI/MCP change; the packed-consumer helper was reviewed by the root.

Closes #3.

[flujo-app]

Independent agent review approved source feecc51 after checking catalog revisions/reset, generic tool bindings, pre-mutation validation and SDK/CLI/MCP surfaces. The reviewer caught a direct-provisioning credential-field gap; it was fixed before the final commit and checked before workspace creation. The root reviewed the separate packed-consumer helper authored by that reviewer. Local required platform/version gates passed as documented in the PR. This records independent agent review, not a separate GitHub account approval.