@guiho/runx 0.2.5 → 0.2.7

package/docs/plans/plans.xdocs.md

@@ -6,20 +6,27 @@ children: []
 files:
   alpha-implementation.md: Breaks the accepted alpha into implementation and validation units.
   citty-cli-migration.md: Executes the full Citty command-tree migration, compatibility validation, protected delivery, and patch release.
+  interactive-init-manifest.md: Sequences the SemVer manifest, public group, scripts directory, and interactive initializer delivery.
   mirror-automatic-push.md: Enables automatic Mirror release pushes with a synchronized protected-main safety gate.
   npm-trusted-publishing-release.md: Sequences workflow implementation, protected delivery, Mirror patching, and public trusted-publishing verification.
+  windows-self-upgrade.md: Sequences synchronous Windows replacement, rollback coverage, validation, issue closure, and patch delivery.
 documents:
   alpha-implementation.md: Plan used for the initial RunX implementation.
   citty-cli-migration.md: Active plan for replacing handwritten CLI parsing and routing with Citty and delivering its patch release.
+  interactive-init-manifest.md: Approved implementation plan for the RunX interactive init manifest feature.
   mirror-automatic-push.md: Approved plan for configuring, validating, and merging Mirror push=true without applying another release.
   npm-trusted-publishing-release.md: Approved executable plan for the RunX 0.2.1 trusted-publishing release trial.
+  windows-self-upgrade.md: Approved executable plan for fixing Windows native self-upgrade and delivering its patch.
 tags:
   - plans
 keywords:
   - runx
   - implementation
   - citty
+  - runx init
+  - scripts directory
   - mirror push
+  - windows self-upgrade
 flags: []
 status: stable
 ---

package/docs/plans/windows-self-upgrade.md

@@ -0,0 +1,129 @@
+---
+name: RunX Windows Self-Upgrade Plan
+purpose: Execute the accepted synchronous and recoverable Windows self-upgrade design.
+description: Sequences executable replacement, regression coverage, documentation, validation, issue closure, and the next Mirror patch.
+created: 2026-07-14
+flags:
+  - approved
+  - executed
+tags:
+  - plans
+  - cli
+  - windows
+keywords:
+  - runx upgrade
+  - executable replacement
+  - rollback
+  - patch release
+owner: runx-plans
+---
+
+# RunX Windows Self-Upgrade Plan
+
+## Sources
+
+- [Windows Self-Upgrade Decision](../decisions/windows-self-upgrade.md)
+- [Alpha Command Catalog Requirements](../requirements/alpha-command-catalog.md)
+- [CLI Architecture](../architecture/cli-architecture.md)
+- GitHub issues `CGuiho/runx#9` and `CGuiho/runx#1`
+
+## Unit 1: Replace the Windows Executable Synchronously
+
+- Goal: Make `upgradeSelf()` return successfully only after the canonical
+  Windows executable path contains and runs the target release.
+- Owner: `C:\GUIHO\runx`.
+- Dependencies: Accepted Windows self-upgrade decision.
+- Files:
+  - `source/self-management.ts`
+  - `source/types.ts` only if the result contract must change
+- Behavior:
+  - Download to `.new`, rename the installed executable to `.old`, install the
+    new file at the original path, and verify `<self-path> --version`.
+  - Return `scheduled: false` after verified replacement.
+  - On failure, remove the failed target, restore `.old`, remove `.new`, and
+    return a non-zero `RunXError` with recovery context.
+  - Delete `.old` immediately when possible; defer only deletion of the locked
+    old image after the current process exits.
+- Data/schema, auth, permissions, and cache: No application data, schema,
+  authentication, authorization, or cache impact. Filesystem write permission
+  to the installed executable remains required.
+- Acceptance: The installed path is the verified target before
+  `upgradeSelf()` resolves and no `.new` file remains.
+- Stop conditions: Stop if Windows cannot rename the running executable, the
+  target cannot be verified, rollback cannot restore the installed path, or
+  unrelated self-management behavior changes.
+
+## Unit 2: Add Regression Coverage
+
+- Goal: Prove the fixed upgrade contract and preserve the already-correct help
+  behavior from issue #1.
+- Dependencies: Unit 1 complete.
+- Files:
+  - `source/guiho-runx.spec.ts` or a focused colocated self-management spec
+  - existing `source/cli.spec.ts` only if help coverage needs correction
+- Checks:
+  - Mock the GitHub latest-release response and downloaded Windows binary.
+  - Configure `RUNX_SELF_PATH` to an isolated executable path.
+  - Assert the replacement exists at that path before the promise resolves,
+    reports `scheduled: false`, runs as the expected version, and leaves no
+    `.new` file.
+  - Force verification failure and assert restoration of the original file.
+  - Run the existing `-h`/`--help` tests outside a manifest directory.
+- Acceptance: Windows CI exercises success and rollback; issue #1 remains
+  covered without changing its implemented behavior.
+- Stop conditions: Stop on nondeterministic process cleanup, leaked test
+  processes, platform-dependent assertions on non-Windows runners, or failure
+  to restore global fetch/environment state.
+
+## Unit 3: Align Documentation and Validate
+
+- Goal: Make public and structured documentation describe completed rather than
+  scheduled Windows replacement, then pass the full release gate.
+- Dependencies: Units 1 and 2 complete.
+- Files:
+  - `DOCS.md`
+  - `source/source.xdocs.md`
+  - `runx.xdocs.md`
+  - accepted decision and plan lifecycle flags when implementation completes
+- Checks:
+  - `bun run typecheck`
+  - `bun test`
+  - `bun run build`
+  - `bun run binary`
+  - `bun run binaries`
+  - `xdocs meta . --documents --strict --owner runx --format json`
+  - `xdocs doctor . --warnings-as-errors --format json`
+  - `git diff --check`
+- Acceptance: All checks pass, docs agree with behavior, and the worktree
+  contains only understood task changes.
+- Stop conditions: Stop on any failed validation or unexpected worktree change.
+
+## Unit 4: Close Issues and Apply the Patch
+
+- Goal: Close both resolved GitHub issues and publish the next
+  Mirror-managed patch state.
+- Dependencies: Unit 3 committed and the worktree clean.
+- Sequence:
+  - Confirm issue #9 acceptance evidence and issue #1 Citty regression evidence.
+  - Close issues #9 and #1 with concise resolution comments.
+  - Run `mirror config show` and `mirror version plan patch`.
+  - Update the configured changelog with the planned next version and commit
+    release preparation.
+  - Run the full typecheck/test gate again if release preparation changes any
+    executable inputs.
+  - Apply `mirror version apply patch --yes`; allow configured commit/push/tag
+    behavior and do not hand-edit Mirror-managed fields.
+- Acceptance: Both issues are closed, the changelog records the fix, and
+  package version, release commit, tag, and configured remote push agree.
+- Stop conditions: Stop if an issue acceptance criterion is unproved, Mirror
+  plans an unexpected version, validation fails, or protected push is rejected.
+
+## TODO Alignment
+
+This is one approved, focused execution session. No additional durable TODO
+entry or delegated component task is required.
+
+## First Executable Unit
+
+Unit 1: implement synchronous Windows replacement and rollback in
+`source/self-management.ts`.

package/docs/reviews/implementation/implementation.xdocs.md

@@ -5,15 +5,22 @@ parent: runx-reviews
 children: []
 files:
   citty-cli-migration-review.md: Reviews the implemented Citty command tree, compatibility adapter, tests, documentation, packaging, and release readiness.
+  interactive-init-manifest-review.md: Reviews the implemented RunX initializer, strict manifest contract, tests, documentation, and delivery readiness.
+  windows-self-upgrade-review.md: Reviews synchronous Windows replacement, rollback, cleanup, tests, CI coverage, and release readiness.
 documents:
   citty-cli-migration-review.md: Accepted implementation review for the full Citty CLI migration.
+  interactive-init-manifest-review.md: Accepted implementation review for the RunX interactive init manifest feature.
+  windows-self-upgrade-review.md: Accepted implementation review for the Windows native self-upgrade fix.
 tags:
   - reviews
   - implementation
 keywords:
   - runx
   - citty
+  - runx init
+  - scripts directory
   - implementation review
+  - windows self-upgrade
 flags: []
 status: stable
 ---

package/docs/reviews/implementation/interactive-init-manifest-review.md

@@ -0,0 +1,69 @@
+---
+name: RunX Interactive Init Manifest Implementation Review
+purpose: Assess the delivered RunX initializer and manifest contract against the accepted decision and plan.
+description: Reviews Citty routing, strict SemVer and group validation, terminal safety, tests, documentation, and delivery boundaries.
+created: 2026-07-14
+flags:
+  - accepted
+tags:
+  - reviews
+  - implementation
+  - cli
+keywords:
+  - runx init
+  - runx.yaml
+  - semantic versioning
+  - public group
+  - scripts directory
+owner: runx-implementation-reviews
+---
+
+# RunX Interactive Init Manifest Implementation Review
+
+## Verdict
+
+Accepted. No blocking, high, medium, or low findings remain.
+
+## Acceptance Criteria Check
+
+- `runx init` is a first-class Citty command, appears in the home/help tree,
+  and is reserved from selector shorthand.
+- The manifest accepts Semantic Versioning `1.x` strings, requires an in-root
+  `scripts.directory` and `public` group, and permits `commands: []` while
+  retaining strict command-group validation.
+- The initializer uses a guided terminal adapter with project and scripts
+  prompts, an exact YAML preview, confirmation, overwrite confirmation, and
+  cancellation behavior. It writes only `runx.yaml`, not `scripts/`.
+- Writes use a same-directory temporary file, validate the temporary manifest,
+  then rename it into place. No configured command is read for execution or
+  spawned by this path.
+- `--file` and `--format json` fail explicitly for `init`; `--cwd` selects the
+  target directory.
+- The README, canonical documentation, source XDocs metadata, and package
+  metadata align with the implementation. The bundled agent skill is unchanged
+  by design; the separate agent-integration follow-up remains issue #11.
+
+## Verification Evidence
+
+- `bun run typecheck` passed.
+- `bun test` passed: 22 tests and 180 assertions, including initialization,
+  cancellation, overwrite, empty-catalog list/check, and non-interactive CLI
+  coverage.
+- `bun run build` and `bun run binary` passed.
+- The compiled `bin/runx.exe --help-tree` includes `init`.
+- XDocs strict metadata checks for `source`, plans, and plan reviews passed;
+  the XDocs tree is intact.
+
+## Residual Risk
+
+The automated environment has no interactive TTY, so the live terminal frame
+was exercised through the injected prompt contract rather than a human session.
+The native binary build and its command-tree smoke check confirm that the
+initializer is included in the compiled executable.
+
+## References
+
+- [Decision](../../decisions/interactive-init-manifest.md)
+- [Plan](../../plans/interactive-init-manifest.md)
+- [Plan Review](../plans/interactive-init-manifest-review.md)
+- GitHub issues [#10](https://github.com/CGuiho/runx/issues/10) and [#11](https://github.com/CGuiho/runx/issues/11)

package/docs/reviews/implementation/windows-self-upgrade-review.md

@@ -0,0 +1,79 @@
+---
+name: RunX Windows Self-Upgrade Implementation Review
+purpose: Review the implemented Windows self-upgrade fix against its accepted decision and plan.
+description: Confirms synchronous replacement, target verification, rollback, cleanup, tests, CI coverage, documentation, and release readiness.
+created: 2026-07-14
+flags:
+  - accepted
+tags:
+  - reviews
+  - implementation
+  - windows
+keywords:
+  - runx upgrade
+  - executable replacement
+  - rollback
+  - windows ci
+owner: runx-implementation-reviews
+---
+
+# RunX Windows Self-Upgrade Implementation Review
+
+## Verdict
+
+Accepted. No blocker, high, medium, or low findings remain.
+
+## Findings
+
+No actionable findings. The implementation matches the approved synchronous
+replacement and recovery design without changing manifest execution, Citty
+routing, uninstall behavior, or non-Windows upgrade behavior.
+
+## Acceptance Criteria
+
+- `upgradeSelf()` renames the running Windows executable, installs the
+  downloaded target at the canonical path, and awaits `<path> --version`.
+- Successful Windows upgrade results report `scheduled: false`.
+- Verification failures remove the invalid replacement and restore `.old`.
+- `.new` is absent after success and rollback.
+- Cleanup retries deletion of the locked `.old` image after the old process
+  releases it.
+- A Windows-only test holds a real copied executable open during replacement,
+  verifies the new binary at the canonical path before completion, and observes
+  backup cleanup.
+- A second Windows test proves rollback after invalid-binary verification.
+- Existing Citty tests continue to prove `-h` and `--help` outside a manifest.
+- The GitHub workflow now runs typecheck, tests, build, and native compilation
+  on `windows-latest` in addition to the existing Linux release-matrix gate.
+
+## Verification Evidence
+
+- `bun run typecheck`: passed.
+- `bun test`: 15 passed, 0 failed, 134 assertions.
+- `bun run build`: passed.
+- `bun run binary`: passed.
+- `bun run binaries`: twelve native assets built and verified.
+- Windows x64 native `-h` outside a manifest: passed.
+- Windows x64 native `--version`: reported `0.2.5` before the release bump.
+- CI workflow YAML parse: passed.
+- `xdocs doctor . --warnings-as-errors --format json`: 0 errors, 0 warnings.
+- `git diff --check`: passed.
+
+## Documentation and TODO
+
+`DOCS.md`, source/root/workflow XDocs descriptors, the accepted decision, plan,
+plan review, this implementation review, and validation evidence are aligned.
+No TODO entry is needed for this completed single-session fix.
+
+## Residual Risk
+
+The new `windows-latest` job cannot execute until the committed workflow reaches
+GitHub. Local Windows coverage exercises the same live-file replacement and
+cleanup behavior. Public upgrade from 0.2.0 to the new patch can only be verified
+after the patch release assets exist.
+
+## References
+
+- [Decision](../../decisions/windows-self-upgrade.md)
+- [Plan](../../plans/windows-self-upgrade.md)
+- [Plan Review](../plans/windows-self-upgrade-review.md)

package/docs/reviews/plans/interactive-init-manifest-review.md

@@ -0,0 +1,82 @@
+---
+name: RunX Interactive Init Manifest Plan Review
+purpose: Verify that the interactive-init implementation plan is executable, safe, and traceable.
+description: Reviews manifest constraints, terminal workflow boundaries, test coverage, XDocs work, and pull-request delivery for runx init.
+created: 2026-07-14
+flags:
+  - approved
+tags:
+  - reviews
+  - plans
+  - cli
+keywords:
+  - runx init
+  - runx.yaml
+  - semantic versioning
+  - public group
+  - scripts directory
+owner: runx-plan-reviews
+---
+
+# RunX Interactive Init Manifest Plan Review
+
+## Verdict
+
+Ready for execution.
+
+## Findings
+
+No blocker, high, medium, or low findings remain.
+
+The plan is traceable to the accepted interactive-init decision, the existing
+command-catalog requirement, and the Citty CLI architecture. The only review
+finding was resolved in the plan: `runx init` is an interactive terminal
+workflow, so `--format json` and `--file` must fail clearly rather than create
+ambiguous output or target files.
+
+## Sequencing and Safety
+
+- Manifest schema changes precede the initializer, so generated YAML is
+  validated by the same strict contract that later commands use.
+- The initializer is isolated from the executor and is explicitly prohibited
+  from spawning configured manifest commands.
+- The prompt boundary is injectable for tests; an interactive terminal is
+  required for the real user interface.
+- Existing-file confirmation, cancellation, and atomic writes prevent silent
+  replacement and partial manifests.
+- The `scripts` directory is configured but not created until a real script is
+  added, matching the accepted file-only initialization boundary.
+- Manifest evolution is constrained to supported SemVer major `1`; no legacy
+  numeric compatibility or migration policy is hidden in the implementation.
+
+## Coverage Review
+
+- Tests cover SemVer, public-group, scripts-directory, empty-catalog, command
+  group-reference, creation, cancellation, overwrite, non-interactive, and
+  unsupported-option behavior.
+- The full Bun typecheck, test, library build, local native compilation, XDocs
+  subtree validation, and diff hygiene are named.
+- Native compilation of the terminal prompt dependency is an explicit stop
+  condition.
+- No API, database, authentication, authorization, cache, cloud, secret,
+  deployment, release, tag, or package-publication work is in scope.
+
+## Documentation and TODO Alignment
+
+The plan updates public CLI documentation and the affected XDocs descriptors.
+The bundled RunX agent skill is deliberately deferred to the separate
+agent-integration feature tracked in issue #11, as directed by the project
+owner. The work is one focused package session, so no additional long-running
+TODO entry is required.
+
+## First Executable Unit
+
+Update `source/manifest.ts` and its tests/fixtures to establish the SemVer,
+scripts-directory, mandatory-public-group, and empty-catalog contract.
+
+## References
+
+- [Plan](../../plans/interactive-init-manifest.md)
+- [Decision](../../decisions/interactive-init-manifest.md)
+- [Requirements](../../requirements/alpha-command-catalog.md)
+- [CLI Architecture](../../architecture/cli-architecture.md)

package/docs/reviews/plans/plans.xdocs.md

@@ -5,12 +5,16 @@ parent: runx-reviews
 children: []
 files:
   citty-cli-migration-review.md: Reviews completeness, compatibility, safety invariants, native packaging, and release sequencing for the Citty migration.
+  interactive-init-manifest-review.md: Reviews the RunX init manifest schema, terminal workflow, tests, XDocs, and pull-request delivery.
   mirror-automatic-push-review.md: Reviews synchronized-main safeguards, read-only validation, protected delivery, and release side effects.
   npm-trusted-publishing-release-review.md: Reviews sequencing, acceptance criteria, safety gates, and validation for the RunX 0.2.1 trusted-publishing plan.
+  windows-self-upgrade-review.md: Reviews synchronous replacement, rollback, regression coverage, issue closure, and patch delivery.
 documents:
   citty-cli-migration-review.md: Ready-for-execution review of the full Citty CLI migration plan.
+  interactive-init-manifest-review.md: Ready-for-execution review of the RunX interactive init manifest plan.
   mirror-automatic-push-review.md: Ready-for-execution review of the Mirror automatic-push configuration plan.
   npm-trusted-publishing-release-review.md: Ready-for-execution review of the npm trusted-publishing release plan.
+  windows-self-upgrade-review.md: Ready-for-execution review of the Windows native self-upgrade fix plan.
 tags:
   - reviews
   - plans
@@ -18,8 +22,11 @@ keywords:
   - runx
   - plan review
   - citty
+  - runx init
+  - scripts directory
   - mirror push
   - trusted publishing
+  - windows self-upgrade
 flags: []
 status: stable
 ---

package/docs/reviews/plans/windows-self-upgrade-review.md

@@ -0,0 +1,71 @@
+---
+name: RunX Windows Self-Upgrade Plan Review
+purpose: Verify that the Windows self-upgrade plan is safe, complete, and executable.
+description: Reviews replacement sequencing, rollback, tests, documentation, issue closure, and Mirror patch delivery.
+created: 2026-07-14
+flags:
+  - approved
+tags:
+  - reviews
+  - plans
+  - windows
+keywords:
+  - runx upgrade
+  - executable replacement
+  - rollback
+  - mirror patch
+owner: runx-plan-reviews
+---
+
+# RunX Windows Self-Upgrade Plan Review
+
+## Verdict
+
+Ready for execution.
+
+## Findings
+
+No blocker, high, medium, or low findings remain. The plan traces to the accepted
+Windows self-upgrade decision and existing native-upgrade requirement. Each unit
+has a bounded outcome, named files, dependencies, acceptance criteria, checks,
+and explicit stop conditions.
+
+## Sequencing and Failure Safety
+
+- Replacement precedes verification, and successful completion requires the
+  canonical path to execute the expected target version.
+- Rollback occurs before any failure is surfaced after the old executable was
+  renamed.
+- Deferred work is limited to deleting the locked old image; replacement itself
+  is complete before success.
+- Issue closure and Mirror application follow implementation validation and a
+  clean committed worktree.
+- The plan recognizes configured Mirror commit, push, and tag side effects and
+  stops on protected-push rejection.
+
+## Coverage Review
+
+- Success, failure, rollback, temporary-file cleanup, and platform isolation are
+  explicit.
+- Existing `-h` coverage directly supports closing issue #1.
+- Typecheck, unit tests, library build, local binary, the twelve-target matrix,
+  strict XDocs checks, and diff hygiene are included.
+- No route, API, UI, data schema, authentication, authorization, cache, cloud,
+  secret, or database work is in scope.
+
+## TODO and Documentation Alignment
+
+The work is a single focused package session and does not need a long-running
+TODO entry. Public `DOCS.md`, source/root XDocs descriptors, lifecycle records,
+and the changelog are included in the correct sequence.
+
+## First Executable Unit
+
+Implement synchronous replacement, target-version verification, rollback, and
+old-image cleanup in `source/self-management.ts`.
+
+## References
+
+- [Plan](../../plans/windows-self-upgrade.md)
+- [Decision](../../decisions/windows-self-upgrade.md)
+- [CLI Architecture](../../architecture/cli-architecture.md)

package/docs/validation/interactive-init-manifest.md

@@ -0,0 +1,79 @@
+---
+name: RunX Interactive Init Manifest Validation
+purpose: Record executable verification evidence for the RunX initializer and strict manifest contract.
+description: Captures typecheck, tests, library and native builds, compiled CLI smoke checks, and XDocs validation for runx init.
+created: 2026-07-14
+flags:
+  - passed
+tags:
+  - validation
+  - cli
+  - manifest
+keywords:
+  - runx init
+  - runx.yaml
+  - bun test
+  - native binary
+  - xdocs
+owner: runx-validation
+---
+
+# RunX Interactive Init Manifest Validation
+
+## Summary
+
+The interactive initializer and strict manifest contract passed all applicable
+local validation gates. No release, version, tag, package publication, cloud,
+or secret operation was performed.
+
+## Scope
+
+- Citty registration and help surfaces for `runx init`.
+- SemVer `1.x`, scripts-directory, `public` group, and empty-command manifest
+  validation.
+- Prompt cancellation, overwrite confirmation, exact generated YAML, atomic
+  write validation, and non-interactive error behavior.
+- User documentation and XDocs metadata.
+
+## Commands Run
+
+| Command | Result | Evidence |
+| --- | --- | --- |
+| `bun run typecheck` | Passed | Strict TypeScript compilation completed without diagnostics. |
+| `bun test` | Passed | 22 tests and 180 assertions passed across CLI, manifest, initializer, and self-management suites. |
+| `bun run build` | Passed | Library output compiled successfully. |
+| `bun run binary` | Passed | Native Windows executable compiled to `bin/runx.exe`. |
+| `bin/runx.exe --help-tree` | Passed | The compiled command tree includes `init`. |
+| `xdocs meta source --strict --format json` | Passed | The new initializer and test files are fully described. |
+| `xdocs meta docs\\plans --documents --strict --format json` | Passed | The plan and companion metadata validate. |
+| `xdocs meta docs\\reviews\\plans --documents --strict --format json` | Passed | The plan review and companion metadata validate. |
+| `xdocs tree` | Passed | The RunX documentation hierarchy is intact. |
+| `git diff --check` | Passed | No whitespace errors were reported before delivery records were added. |
+
+## Manual Checks
+
+- The generated empty manifest has the required version, project, scripts,
+  `public` group, and `commands: []` shape.
+- No empty `scripts/` directory is created by initialization.
+- `runx init --file ...` and `runx init --format json` return explicit errors
+  without creating a manifest.
+
+## Skipped Checks
+
+A person-driven interactive terminal session could not be run in this automated
+non-TTY environment. The initializer’s prompt sequence is covered through its
+injected prompt adapter; the compiled executable was smoke-tested for command
+registration.
+
+## Readiness
+
+Ready for code review and a draft pull request. The bundled agent-skill
+automation remains intentionally outside this change and is tracked by issue
+#11.
+
+## References
+
+- [Decision](../decisions/interactive-init-manifest.md)
+- [Plan](../plans/interactive-init-manifest.md)
+- [Implementation Review](../reviews/implementation/interactive-init-manifest-review.md)
+- GitHub issue [#10](https://github.com/CGuiho/runx/issues/10)

package/docs/validation/validation.xdocs.md

@@ -6,17 +6,24 @@ children: []
 files:
   alpha-implementation-summary.md: Records the completed alpha implementation, checks, and release boundaries.
   citty-cli-migration.md: Records the complete local validation gate for the Citty command-tree migration.
+  interactive-init-manifest.md: Records validation evidence for the interactive initializer and strict manifest contract.
+  windows-self-upgrade.md: Records Windows replacement, rollback, cleanup, native build, CI, and XDocs validation evidence.
 documents:
   alpha-implementation-summary.md: Validation summary for the first RunX implementation.
   citty-cli-migration.md: Validation evidence for TypeScript, tests, native assets, npm packaging, CLI behavior, and XDocs.
+  interactive-init-manifest.md: Validation evidence for the RunX interactive init manifest feature.
   npm-trusted-publishing-0.2.2.md: Validation evidence for the blocked 0.2.2 npm trusted-publishing retry.
+  windows-self-upgrade.md: Validation evidence for GitHub issues #9 and #1 and the Windows self-upgrade patch.
 tags:
   - validation
 keywords:
   - runx
   - citty
+  - runx init
+  - scripts directory
   - tests
   - summary
+  - windows self-upgrade
 flags: []
 status: stable
 ---