kindred/silo-mod
1
1
Fork 0
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

feat(silo): BOM auto-extraction from Assembly links (#276) #49

Merged
forbes merged 1 commits from feat/bom-sync-and-manifest into main 2026-02-19 20:27:16 +00:00
Conversation 0 Commits 1 Files Changed 3 +404 -1
forbes commented 2026-02-19 20:27:08 +00:00
Owner
Copy Link

Phase 1 implementation:

  • New bom_sync.py: extract cross-document App::Link components from
    Assembly, resolve SiloItemId UUIDs to part numbers, diff against
    server BOM, apply adds/qty updates via individual CRUD calls.
  • Hook _push_bom_after_upload into Silo_Save and Silo_Commit
    (same non-blocking pattern as DAG sync).
  • Hook _update_manifest_revision to write revision_hash into .kc
    manifest after successful upload (#277).
  • Add bom_merged SSE signal + dispatch + Activity pane handler.
  • Add merge_bom_json to SiloClient (forward-looking for Phase 2).

Merge rules: auto-add, auto-update qty, NEVER auto-delete removed
entries (warn only).

Refs: #276, #277

Phase 1 implementation: - New bom_sync.py: extract cross-document App::Link components from Assembly, resolve SiloItemId UUIDs to part numbers, diff against server BOM, apply adds/qty updates via individual CRUD calls. - Hook _push_bom_after_upload into Silo_Save and Silo_Commit (same non-blocking pattern as DAG sync). - Hook _update_manifest_revision to write revision_hash into .kc manifest after successful upload (#277). - Add bom_merged SSE signal + dispatch + Activity pane handler. - Add merge_bom_json to SiloClient (forward-looking for Phase 2). Merge rules: auto-add, auto-update qty, NEVER auto-delete removed entries (warn only). Refs: #276, #277
forbes added 1 commit 2026-02-19 20:27:09 +00:00
feat(silo): BOM auto-extraction from Assembly links (#276) f67d9a0422 
Phase 1 implementation:
- New bom_sync.py: extract cross-document App::Link components from
  Assembly, resolve SiloItemId UUIDs to part numbers, diff against
  server BOM, apply adds/qty updates via individual CRUD calls.
- Hook _push_bom_after_upload into Silo_Save and Silo_Commit
  (same non-blocking pattern as DAG sync).
- Hook _update_manifest_revision to write revision_hash into .kc
  manifest after successful upload (#277).
- Add bom_merged SSE signal + dispatch + Activity pane handler.
- Add merge_bom_json to SiloClient (forward-looking for Phase 2).

Merge rules: auto-add, auto-update qty, NEVER auto-delete removed
entries (warn only).

Refs: #276, #277
forbes merged commit 43e905c00a into main 2026-02-19 20:27:16 +00:00
forbes deleted branch feat/bom-sync-and-manifest 2026-02-19 20:27:16 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
bug
Something isn't working
 debugging
Debugging and diagnostics
 enhancement
New feature or request
 priority:high
High priority
 ui
User interface
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
forbes
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kindred/silo-mod#49
Delete Branch "feat/bom-sync-and-manifest"

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?