Archive command moves changes to incorrect path (openspec/changes/archive)

[otakai]

This bug was reproduced in version 0.17.2 of @fission-ai/openspec.

Description:
The openspec archive command moves the change directory to openspec/changes/archive/<date>-<name>.
However, the project structure and other parts of the CLI (like item-discovery.js) expect archived changes to reside in openspec/archive/.
This causes the archived change to be "lost" or misplaced, and subsequent commands like openspec list or validation checks fail to find it correctly or clutter the changes/ directory.

Environment:

• Package: @fission-ai/openspec@0.17.2
• Node: >=20.19.0
• OS: Windows

Reproduction:

1. Initialize a project with openspec init.
2. Create a change with openspec scaffold fix-something.
3. Run openspec archive fix-something.
4. Observe that openspec/changes/fix-something moves to openspec/changes/archive/... instead of openspec/archive/....

Proposed Fix:
The implementation in dist/core/archive.js incorrectly joins changesDir instead of targetPath (project root) when defining archiveDir.

In openspec/dist/core/archive.js:

// Current (Buggy)
const archiveDir = path.join(changesDir, 'archive');

// Fixed
const archiveDir = path.join(targetPath, 'openspec', 'archive');

Also, item-discovery.js needs alignment if it isn't already looking in the root archive folder.

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Possible Duplicates

• ISSUE-197

Related Issues

• Error: EPERM: operation not permitted, rename......But in fact, there is no file occupancy or permission problem at all, and the pwsh command is successful. #197
• Archive command fails when creating new spec file with REMOVED Requirements #403
• Feature request: automatically update project.md during archive #331
• Bug: Command arguments not being passed to .opencode/command templates #153
• Bug: Archive validation fails despite requirement headers containing SHALL/MUST #159
• [Suggestion for Opencode Command] - Archiver Archived wrong Proposal #151

🔗 Related PRs

#283 - Fix Cline: use workflows instead of rules for slash commands [merged]
#335 - fix(opencode): remove hardcoded agent field from slash commands [merged]
#404 - Fix: Allow REMOVED requirements when creating new spec files (#403) [merged]
#407 - fix(artifact-graph): normalize paths for cross-platform glob compatibility [merged]
#408 - feat: add change creation utilities [closed]

👤 Suggested Assignees

• TabishB
• smileeunsong
• cheese-custard
• BobbyWang0120
• IgorWarzocha

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[TabishB]

@otakai openspec/changes/archive is the correct path when archiving.

However, the project structure and other parts of the CLI (like item-discovery.js) expect archived changes to reside in openspec/archive/.

This is unexpected though, I'll take a look.