kindred/create
1
1
Fork 0
Code Issues 53 Pull Requests Actions Packages Projects 9 Releases 2 Wiki Activity

feat(kc): populate manifest silo_instance and revision_hash fields #277

New Issue
Closed
opened 2026-02-19 06:48:07 +00:00 by forbes · 0 comments
forbes commented 2026-02-19 06:48:07 +00:00
Owner
Copy Link

Summary

kc_format.py creates silo/manifest.json on first save but leaves silo_instance and revision_hash as null. These should be populated from Silo server context.

Current behavior

  • silo_instance: always null
  • revision_hash: always null

Expected behavior

  • silo_instance: set to the Silo server URL when the document is registered/committed
  • revision_hash: set to the revision hash returned by the server after each commit

Additional KC spec gaps

  • history.json: read-only (never written back to ZIP)
  • approvals.json: read-only
  • dependencies.json: read-only
  • silo/inspection/ directory: not implemented
  • silo/thumbnails/ directory: not implemented

References

  • docs/KC_SPECIFICATION.md — full format spec (Layers 2-4)
  • src/Mod/Create/kc_format.py — current manifest creation logic
## Summary kc_format.py creates silo/manifest.json on first save but leaves silo_instance and revision_hash as null. These should be populated from Silo server context. ## Current behavior - silo_instance: always null - revision_hash: always null ## Expected behavior - silo_instance: set to the Silo server URL when the document is registered/committed - revision_hash: set to the revision hash returned by the server after each commit ## Additional KC spec gaps - history.json: read-only (never written back to ZIP) - approvals.json: read-only - dependencies.json: read-only - silo/inspection/ directory: not implemented - silo/thumbnails/ directory: not implemented ## References - docs/KC_SPECIFICATION.md — full format spec (Layers 2-4) - src/Mod/Create/kc_format.py — current manifest creation logic
forbes added the enhancement label 2026-02-19 06:48:07 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
UX
branding
bug
ci/cd
CI/CD workflows and deployment
 defaults
documentation
Developer documentation
 enhancement
high-priority
low-priority
theme
No Label enhancement
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/create#277
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?