diff --git a/.kiro/specs/xce-test-rc-file/spec.json b/.kiro/specs/xce-test-rc-file/spec.json index ad2b211a..1dc305f6 100644 --- a/.kiro/specs/xce-test-rc-file/spec.json +++ b/.kiro/specs/xce-test-rc-file/spec.json @@ -1,9 +1,9 @@ { "feature_name": "xce-test-rc-file", "created_at": "2026-08-26T08:49:11Z", - "updated_at": "2026-08-26T09:18:22Z", + "updated_at": "2026-08-26T17:34:17Z", "language": "en", - "phase": "tasks-generated", + "phase": "implementation-complete", "approvals": { "requirements": { "generated": true, diff --git a/.kiro/specs/xce-test-rc-file/tasks.md b/.kiro/specs/xce-test-rc-file/tasks.md index 6a7df21d..676ebc00 100644 --- a/.kiro/specs/xce-test-rc-file/tasks.md +++ b/.kiro/specs/xce-test-rc-file/tasks.md @@ -1,6 +1,6 @@ # Implementation Plan -- [ ] 1. Foundation: rc-file path resolution and line-loading capability +- [x] 1. Foundation: rc-file path resolution and line-loading capability - [x] 1.1 Implement rc-file path resolution following XDG precedence, with unit tests - Resolve the rc-file location using the XDG config variable when it is set and non-empty - Fall back to the home-directory XDG default when that variable is unset or empty, and to "no resolvable path" when neither variable is usable @@ -16,7 +16,7 @@ - Observable: a unit test run demonstrates every line is processed when the runner keeps succeeding, remaining lines are skipped the first time the runner signals a stop, the runner is never invoked when the file is absent, and a line well beyond a typical small fixed-buffer size (e.g. >4KB) reaches the runner intact and unsplit - _Requirements: 1.2, 1.3_ -- [ ] 2. Core: xce_test startup integration +- [x] 2. Core: xce_test startup integration - [x] 2.1 Add a flag that skips rc-file loading for a single invocation - Register the flag with xce_test's existing command-line option parsing so it is documented in xce_test's own help output - When the flag is given, record that rc-file loading should be skipped for this run @@ -32,7 +32,7 @@ - _Depends: 1.1, 1.2_ - _Boundary: test.c::main_ -- [ ] 3. Validation: end-to-end behavior against the built binary +- [x] 3. Validation: end-to-end behavior against the built binary - [x] 3.1 Verify rc-file discovery, loading, and skip-flag behavior end-to-end - Scenario: a valid rc file's settings/context take effect in both a piped run and an interactive run - Scenario: the skip flag leaves default settings untouched even with a valid rc file present