Skip to content

chore(WIN-001): archive spec post-merge#72

Merged
mlorentedev merged 1 commit into
mainfrom
chore/archive-WIN-001
May 21, 2026
Merged

chore(WIN-001): archive spec post-merge#72
mlorentedev merged 1 commit into
mainfrom
chore/archive-WIN-001

Conversation

@mlorentedev
Copy link
Copy Markdown
Owner

@mlorentedev mlorentedev commented May 21, 2026

Summary

Test plan

  • Spec-gate accepts (no public-contract diff; only files under specs/).
  • Bats suite unaffected.

Mechanical archive via scripts/archive-spec.ps1. Frontmatter updated to
status: archived + merged_pr: 71. Folder moved from specs/ to specs/archive/.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
@mlorentedev mlorentedev merged commit 79cbe63 into main May 21, 2026
6 checks passed
@mlorentedev mlorentedev deleted the chore/archive-WIN-001 branch May 21, 2026 05:24
mlorentedev added a commit that referenced this pull request May 22, 2026
REFACTOR-002 shipped in PR #64 (env-contract path declarations) on
2026-05-20 but its spec folder was missed by the archive bundle PR #88
(2026-05-21 session close). Move to specs/archive/ to keep the active
specs/ directory accurate (only WIN-002-windows-smoke-sweep remains
genuinely open).

Same chore-close-spec-lifecycle pattern as PR #66 (TERM-001) and PR #72
(WIN-001): pure git-mv, no production code touched.
mlorentedev added a commit that referenced this pull request May 22, 2026
…t flow (#91)

* chore(REFACTOR-002): archive spec folder post-merge (PR #64)

REFACTOR-002 shipped in PR #64 (env-contract path declarations) on
2026-05-20 but its spec folder was missed by the archive bundle PR #88
(2026-05-21 session close). Move to specs/archive/ to keep the active
specs/ directory accurate (only WIN-002-windows-smoke-sweep remains
genuinely open).

Same chore-close-spec-lifecycle pattern as PR #66 (TERM-001) and PR #72
(WIN-001): pure git-mv, no production code touched.

* feat(REFACTOR-004): wire init-repo-* helpers into init-project default flow

AUDIT-005 (specs/archive-pending in vault) surfaced that
init-repo-{agents,standards,github-defaults}.{sh,ps1} -- created in
2026-05-14 via SDD-010 + SDD-013 -- have zero recorded invocations in
shell history. Built-but-unused: the spec lifecycle confirmed code
exists, but the value never landed in user practice.

This PR wires the three helpers into the default init-project.{sh,ps1}
flow so they actually fire when bootstrapping a new repo. Each
invocation is non-fatal (individual failure logs a warning and
continues, does not abort init). New opt-out flags --skip-agents /
--skip-standards / --skip-github (PS: -SkipAgents / -SkipStandards /
-SkipGithub) preserve the previous behaviour for users who want it.
init-repo-github-defaults is auto-skipped when no `origin` remote is
configured (typical for a brand-new local repo) -- silent info log.

The three standalone helper scripts themselves are bit-identical to
pre-PR state. Their independent CLI invocation continues to work for
users who run them manually on an existing repo.

Cross-OS surface:
- scripts/init-project.sh: arg parser shift to handle --skip-* flags
  before positional args (preserves existing `project-name stack`
  signature); wiring block inserted after .gitignore creation.
- scripts/init-project.ps1: 3 [switch] params added; wiring block
  inserted before the SUMMARY section; ASCII-only (no em-dash, no
  smart quotes) per PSScriptAnalyzer rule.

Tests: 9 new structural / parity bats asserts in tests/init-project.bats
(flag-parser greps, helper-presence asserts, origin-check guard,
non-fatal log_error count, PS switch presence). Full suite:
765 -> 774 PASS, 0 regressions. Existing 2 functional tests (3, 4)
that exercise the full flow still pass -- confirming `|| log_error
... continuing` correctly handles the missing-vault-template case in
test isolation.

Spec: specs/REFACTOR-004-init-project-repo-wiring/{proposal,tasks,verification}.md
Vault: 11-tasks.md REFACTOR-004 entry (downstream of REFACTOR-001 audit).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant