SurveyCore

Keep SurveyCore HTTP handlers, response schemas, SDK docs, README examples, and tests aligned. Use when routes, request bodies, error codes, response fields, pagination behavior, or config-generation output change.

Keep SurveyCore runtime configuration contracts aligned across models, defaults, validation, execution shaping, example configs, SDK schemas, and tests. Use when config fields, defaults, validation rules, or question-entry semantics change.

Scaffold a new SurveyCore provider capability with the right package split and wiring. Use when adding a new provider, a new parser path, a new answer-builder capability, or a provider-specific question behavior without spreading platform branches across shared packages.

Build and run the smallest credible regression plan for SurveyCore provider changes. Use when parser, answer builder, submitter, proxy, scheduler, or provider detection code changes and you need proof that one platform fix did not break the others.

Port fixes from the SurveyController desktop repo into SurveyCore without copying GUI noise. Use when a user mentions an upstream commit, release, parser breakage, provider regression, or asks whether a desktop-side fix also needs to land in SurveyCore.