docs(dirty-content-fingerprint): mark task 2 container checkbox complete
Both sub-tasks 2.1 and 2.2 were already done and committed; the container checkbox itself was missed during the task loop. All 21 checkboxes (16 leaf tasks + 5 container headers) are now marked complete. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
parent
f4d2c123fd
commit
aaca376868
1 changed files with 1 additions and 1 deletions
|
|
@ -5,7 +5,7 @@
|
|||
- Observable confirmed live (independently re-verified by review, fresh scratch build): a bare `meson setup` with zero `-D` options configures cleanly (73 targets); all 542 C compile commands contain the new define (empty string), matching the existing two defines' counts exactly; no consumption code touched yet
|
||||
- _Requirements: 1.1, 5.1_
|
||||
|
||||
- [ ] 2. Foundation: compute real fingerprint values at both build entry points
|
||||
- [x] 2. Foundation: compute real fingerprint values at both build entry points
|
||||
- [x] 2.1 (P) xce-build.sh computes the dev-loop fingerprint, independently of commit_id
|
||||
- `dirty_fingerprint` computed via `git diff HEAD` + `git ls-files -z --others --exclude-standard | LC_ALL=C sort -z` content, `sha256sum` truncated to 8 hex chars; empty on a clean tree or on computation failure (3 independently-verified graceful-degradation paths: mktemp failure, sha256sum failure, git diff failure -- none abort the script despite `set -euo pipefail`); zero working-tree/index mutation (read-only git invocations only); `commit_id`'s own computation left byte-for-byte untouched
|
||||
- Observable confirmed live (independently re-verified by review, real builds with HEAD pinned to control for concurrent background commits): editing a tracked file and rebuilding produces a fingerprint; different content produces a different fingerprint; reverting to the first edit's exact bytes reproduces the first fingerprint exactly; a `.gitignore`-matched `*.bak` file leaves the fingerprint unchanged; `commit_id`'s `-dirty` suffix stayed intact across every build; every profile (asan/debug/release) carries the option; the original feature's unmodified `test-build-version-regression.sh` passes twice in full (asan+debug)
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue