chihlasm/resolutionflow
1
0
Fork 0
Code Issues 23 Pull Requests 1 Actions Packages Projects Releases Wiki Activity

[Backend] Custom Steps Enhancement - Usage Tracking #38

New Issue
Closed
opened 2026-02-07 22:49:38 +00:00 by chihlasm · 1 comment
chihlasm commented 2026-02-07 22:49:38 +00:00 (Migrated from github.com)
Copy Link

Enhance session custom_steps JSONB field to track step library usage and enable future save session as tree feature.

Design Document: docs/plans/2026-02-07-foundational-schema-design.md (Part 2)

JSONB Enhancement (No Migration Required)

Add optional fields to custom_steps array for tracking:

  • source: ad-hoc | step-library | forked-tree
  • source_step_id: UUID if from library
  • inserted_at: ISO datetime
  • inserted_after_node_id: tree node ID

Pydantic Schema Update

Add fields to CustomStepSchema with defaults for backward compatibility

Usage Tracking Logic

When engineer inserts library step into session:

  1. Add to custom_steps with full metadata
  2. Create StepUsageLog entry immediately
  3. Increment StepLibrary.usage_count
  4. Multiple insertions create multiple log entries

Step Library Reference Handling

  • Deleted steps: source_step_id remains (orphaned UUID)
  • No FK constraint (data in JSONB)
  • Analytics can count historical usage

Acceptance Criteria

  • CustomStepSchema updated with new fields
  • Old sessions load without error (backward compat)
  • Insert from library creates StepUsageLog entry
  • usage_count incremented correctly
  • Multiple insertions counted separately
  • source_step_id preserved after step deletion
  • Ad-hoc steps default to source=ad-hoc

Related: Issues #4-#7 partial, foundational schema work

Enhance session custom_steps JSONB field to track step library usage and enable future save session as tree feature. Design Document: docs/plans/2026-02-07-foundational-schema-design.md (Part 2) JSONB Enhancement (No Migration Required) Add optional fields to custom_steps array for tracking: - source: ad-hoc | step-library | forked-tree - source_step_id: UUID if from library - inserted_at: ISO datetime - inserted_after_node_id: tree node ID Pydantic Schema Update Add fields to CustomStepSchema with defaults for backward compatibility Usage Tracking Logic When engineer inserts library step into session: 1. Add to custom_steps with full metadata 2. Create StepUsageLog entry immediately 3. Increment StepLibrary.usage_count 4. Multiple insertions create multiple log entries Step Library Reference Handling - Deleted steps: source_step_id remains (orphaned UUID) - No FK constraint (data in JSONB) - Analytics can count historical usage Acceptance Criteria - CustomStepSchema updated with new fields - Old sessions load without error (backward compat) - Insert from library creates StepUsageLog entry - usage_count incremented correctly - Multiple insertions counted separately - source_step_id preserved after step deletion - Ad-hoc steps default to source=ad-hoc Related: Issues #4-#7 partial, foundational schema work
chihlasm commented 2026-02-08 00:40:54 +00:00 (Migrated from github.com)
Copy Link

Completed in PR #39. CustomStepSchema updated with source (ad-hoc/step-library/forked-tree), source_step_id, inserted_at, and inserted_after_node_id fields. Backward compatible with existing session JSONB data.

Completed in PR #39. `CustomStepSchema` updated with `source` (ad-hoc/step-library/forked-tree), `source_step_id`, `inserted_at`, and `inserted_after_node_id` fields. Backward compatible with existing session JSONB data.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
10x-analysis
From 10x product analysis
 backend
FastAPI/Python work
 bug
Something isn't working
 collaboration
Team sharing, escalation, notifications
 database
PostgreSQL/schema changes
 documentation
Documentation updates
 duplicate
This issue or pull request already exists
 enhancement
Improvement to existing feature
 feature
New functionality
 frontend
React work
 good first issue
Good for newcomers
 help wanted
Extra attention is needed
 integration
PSA, external service integrations
 intelligence
Analytics, AI, data-driven features
 invalid
This doesn't seem right
 priority: high
Do this soon
 priority: low
Nice to have
 priority: medium
Important but not urgent
 question
Further information is requested
 quick-win
Low effort, high value
 strategic
Long-term strategic bet
 ux
User experience improvements
 wontfix
This will not be worked on
No Label backend priority: high
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
chihlasm
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: chihlasm/resolutionflow#38
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?