PR/issue backlog triage — closed work & salvage map #87
meekmachine
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Context
This is the salvage map from the Jul 20, 2026 PR/issue backlog triage across Polymer, LoomLarge, and Loom3, aligned to Society-of-Mind /
agencySociety.Coverage was the full open backlog on that pass (Polymer issues+PRs, LoomLarge issues+PRs, Loom3 issues+PRs), not only the agency cluster. Product UI outside
agencySocietywas mostly left alone unless it was a clear duplicate/stale draft.Do not invent from memory — reopen from branches or redo on current
mainusing this map.Lace frame correction (important)
Triage initially closed #702 in favor of #727. That was backwards.
If you see older comments saying “use #727”, ignore them. Keep working on #702.
Merged recently (landed — not salvage)
Useful as “what already shipped,” not as reopen targets.
Polymer
agencySocietyschema +DEFAULTseed (#63/#64)LoomLarge
Loom3
Superseded PRs — use the survivor
Do not reopen #736 / #743 / #636 / #727 / #45 / #46. Cherry-pick only if #740/#739/#702 miss a specific commit you need.
Closed as obsolete / wrong home
Latticework-as-home / XState→Most migrations (LoomLarge)
Closed — agencies live in Polymer under epic #60; host should not re-home Latticework agencies.
Polymer first-port duplicates
Loom3 wrong-home planners
Latticework / Polyester PRs (do not revive)
loomlarge_lolLatticework runtime load (obsolete path)Reuse rule: ideas about agency behavior may inform Polymer ports; do not cherry-pick Latticework package wiring or Polyester pins.
Combined / absorbed into surviving issues
Abandoned / stale drafts (closed)
Generic close reason: orphaned under Polymer
agencySocietyhost plan — reopen branch only if still needed, else redo on currentmain.LoomLarge
#685, #684, #683, #679, #677, #676, #651, #647, #642, #634, #618, #555, plus earlier Firebase billing draft #720 (staying on Firebase; replace with minimal main-based fix).
Loom3
#137, #117, #115, #113, #79
Polymer out-of-scope
Salvage later — concrete reuse map
Branches were left in place. Prefer ideas + selective cherry-picks over reopening whole stacks on dead bases.
codex/657-remote-control-modernizationcodex/document-character-authoring-systemagencySocietycodex/speech-saved-voice-defaultcodex/645-emote-animation-synccodex/local-character-profile-fixturescodex/base-pose-uicodex/fbx-import-retargetcodex/annotation-authoring-apiscodex/character-config-presetIdeas only — do not revive stacks: older bone UI spikes LL #332, #330, #329, #231, #230.
Key survivors still open (cross-links)
Polymer
LoomLarge (host track)
Loom3
Suggested execution order (unchanged)
Bottom line
mainover resurrecting dirty stacks.Beta Was this translation helpful? Give feedback.
All reactions