Module enhance_settings 

EnhanceSetting HTTP CRUD (/v1/enhance-settings*). EnhanceSetting HTTP CRUD (= K-V store entry + BPStore commit orchestration).

• POST /v1/enhance-settings — create (body = EnhanceSettingInput, includes data)
• GET /v1/enhance-settings/:id — read (= EnhanceSetting = Ref form)
• PUT /v1/enhance-settings/:id — update (body = EnhanceSettingInput)
• DELETE /v1/enhance-settings/:id — delete (= K-V only; BPStore history remains)
• GET /v1/enhance-settings — list ids

The POST/PUT input form is [EnhanceSettingInput] (= Blueprint embedded with data). Inside the server, into_ref() splits it into (Blueprint, EnhanceSetting Ref form); the BP is committed via BPStore.write_new first, then setting_store.put (= BP first, setting second, so a failed BP commit does not leave an orphan setting). Response / read return EnhanceSetting (= BlueprintId Ref + ttl_secs + meta).

Current scope:

• Consecutive PUTs of the same content produce duplicate commits in BP history (= idempotency is a carry).

Structs

EnhanceSettingsState

Router state for the /v1/enhance-settings* handlers.

Functions

build_enhance_settings_router

Builds the /v1/enhance-settings* router. See the module doc for the commit-then-K-V-write ordering and the POST/PUT input shape.