Prepare Schemeta for dependable multi-user SaaS operation and AI tool integration.
Scope
Add robust API auth/session handling and usage controls.
Add rate limiting, audit logging, and structured error telemetry.
Define MCP-facing tool contracts and schema/versioning guarantees.
Add workspace persistence primitives (autosave, version history checkpoints).
Acceptance Criteria
API/MCP contracts are versioned and backward compatibility policy is documented.
Operational guardrails are in place for abusive/malformed traffic.
Error observability supports fast triage in production.
End-to-end tests cover save/load/restore and API compile/analyze flows.
## Objective
Prepare Schemeta for dependable multi-user SaaS operation and AI tool integration.
## Scope
- Add robust API auth/session handling and usage controls.
- Add rate limiting, audit logging, and structured error telemetry.
- Define MCP-facing tool contracts and schema/versioning guarantees.
- Add workspace persistence primitives (autosave, version history checkpoints).
## Acceptance Criteria
- API/MCP contracts are versioned and backward compatibility policy is documented.
- Operational guardrails are in place for abusive/malformed traffic.
- Error observability supports fast triage in production.
- End-to-end tests cover save/load/restore and API compile/analyze flows.
Rbanh
added this to the Phase 4 - AAA SaaS Productization and UX Polish milestone 2026-02-18 21:51:37 -05:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Objective
Prepare Schemeta for dependable multi-user SaaS operation and AI tool integration.
Scope
Acceptance Criteria
Completed in commit
31a4734.Delivered:
x-request-idheader +request_idin envelopes).docs/api-mcp-contracts.md) with compatibility/versioning guarantees.Validation:
node --check src/server.jsnode --check src/mcp-server.jsnpm testnpm run test:ui