Help wanted: print-support capability pack (designed-in support fins)

[enricopiovesan]

We opened a registry initiative for a manufacturing-shaped capability pack: governed designed-in print support (mesh codecs, overhang analysis, orientation scoring, breakaway fins, sway braces, export gate, bed pad).

Value is still discover → execute → trace — agents must not freestyle scores, fin geometry, or “safe to export.”

Umbrella

• registry#596 — Initiative: print-support

Help wanted (one capability per PR)

Issue	Capability	Notes
#597	print.mesh-parse	STL/3MF → mesh IR
#598	print.mesh-write	mesh IR → STL/3MF
#599	print.overhangs-analyze	overhangs + bed reachability
#600	print.orientation-score	good first issue
#602	print.fins-generate	breakaway fins
#601	print.sway-braces-generate	tall-part braces
#603	print.export-gate	good first issue
#604	print.bed-pad-generate	v1 bbox pad

All labeled help wanted · enhancement · no-spec-needed (plus good first issue where noted).

Rules of the door

• Capability pack only — apps are not ready; no app rewrite PRs
• Fork + PR; one capability per PR; human review; registry CI gates
• Today’s execution boundary is stdin/stdout JSON (no ambient filesystem)
• Skill path welcome: traverse-capability-author
• Domain inspiration only (e.g. Support Fins / Slant3D technique) — do not copy third-party source

Comment on the issue you want, keep the PR to the done-when, wait for CI.

Related earlier contributor door: Discussion #1374.

[enricopiovesan]

Public surfaces for this living pack are up:

• Blog: https://traverse-framework.com/blog/print-support-domain-pack.html
• Q&A: https://traverse-framework.com/questions/what-is-the-print-support-capability-pack.html

Still a designed pack — none of the print.* capabilities are published yet. Help-wanted tickets above remain the contribution path.