v1.2.5.0 — workflows-code--opencode: Phase 17 Alignment + Template Fix

This release infrastructure work domain detection fixing root cause of memory files being saved to incorrect spec folders when working on shared infrastructure. It focuses on making the project setup more consistent and easier to work with.

---

What Changed

Detect_work_domain() function

The project needed a cleaner setup for Detect_work_domain() function. New function that analyzes file paths from observations to detect infrastructure vs project work: calculates ratio of .opencode/ files, identifies subpath , returns domain info with confidence score and matching patterns. This matters because setup and maintenance are easier to manage.

Calculate_alignment_score_with_domain() function

The project needed a cleaner setup for Calculate_alignment_score_with_domain() function. Wraps base scoring with infrastructure awareness: applies +40 bonus to folders matching infrastructure patterns, patterns mapped per subpath. This matters because setup and maintenance are easier to manage.

Validate_content_alignment() and validate_folder_alignment()

The project needed a cleaner setup for Validate_content_alignment() and validate_folder_alignment(). Now use domain-aware scoring: show infrastructure mismatch warning when detected, list better-matching alternatives with boosted scores. This matters because setup and maintenance are easier to manage.

Step 3: Validate Content vs Folder Alignment

The team needed stronger proof that Step 3: Validate Content vs Folder Alignment worked as expected. Added validation of key_files against spec_folder before recovery. This matters because the team has clearer proof that the change works.

Step numbering

Step numbering was no longer needed in its old form. Removed half-steps (2.5 to 3, renumbered subsequent steps). This matters because the project becomes smaller and easier to maintain.

KEY FILES in recovery summary

The team needed stronger proof that KEY FILES in recovery summary worked as expected. Added so users can verify spec folder makes sense for the work. This matters because the team has clearer proof that the change works.

---

Files Changed

File	What Changed
.opencode/	Referenced in the original changelog.
alignment-validator.js	Referenced in the original changelog.
skill/system-spec-kit	Referenced in the original changelog.
command/memory	Referenced in the original changelog.
agent/	Referenced in the original changelog.
continue.md	Referenced in the original changelog.