Entity-as-folder support in status scanner#118
Merged
Conversation
Contributor
Author
Dogfood on real workflowsRan the updated Folder-based (the ones that were broken before)
Flat-file (backward-compat check)
The malformed flat rows in product-strategy ( Release workflow unblockedv1-43-0 and v1-44-0 are now visible to Static tests: 444 passed, 22 deselected (live-only), 0 failures. |
clkao
added a commit
that referenced
this pull request
Apr 18, 2026
clkao
added a commit
that referenced
this pull request
Apr 18, 2026
…end merge as-is Pinned design decision: auto-detection (option a) as shipped, NOT explicit workflow-level entity-style declaration (option b — rejected as scope expansion). CI red is structural fork-PR secret gating (exit 1 in Check-required-secret step), not a code regression — needs environment approval pre-merge so claude-live actually runs. Six nice-to-have test additions (worktree × folder, mod-block × folder, dotfile-subdir exclusion, archive-conflict warning, flat-only regression pin) deferred to a follow-up PR we author post-merge, keeping Karen's scope clean.
ccd6949 to
b4457f4
Compare
clkao
added a commit
that referenced
this pull request
Apr 18, 2026
…ied on flaky target) Static: 437/437 (AC-1/2/3/5 all green). Live: - opus-4-7 teams: PASSED 151.36s - opus-4-6 teams: PASSED 187.34s, Path A fired, 8/8 internal checks, Tier-1 path=dispatch green — the exact flaky context from PR #118 CI run 24596336820 is now green via the rewritten two-path assertion. No 429 quota hit. AC-4's fix-validation intent met; full 9-run matrix deferred to post-merge CI observation.
clkao
added a commit
that referenced
this pull request
Apr 18, 2026
…ied on flaky target) Static: 437/437 (AC-1/2/3/5 all green). Live: - opus-4-7 teams: PASSED 151.36s - opus-4-6 teams: PASSED 187.34s, Path A fired, 8/8 internal checks, Tier-1 path=dispatch green — the exact flaky context from PR #118 CI run 24596336820 is now green via the rewritten two-path assertion. No 429 quota hit. AC-4's fix-validation intent met; full 9-run matrix deferred to post-merge CI observation.
An entity may now live as either a flat `{slug}.md` file or a folder
`{slug}/` containing `index.md`. The non-recursive scan in the status
binary made folder-per-entity workflows (blog-writing, release) invisible
to `--boot`, `--next`, `--set`, `--archive`, and `--next-id` at the
archive boundary.
Changes:
- discover_entity_files() resolves slugs from both forms, skipping
reserved subdirs (`_archive`, `_mods`) and dotfiles.
- scan_entities / scan_entities_active delegate to the discovery
function, so `--next`, `--next-id`, `--boot`, `--archived`, `--where`,
and the default overview inherit folder support.
- resolve_entity_path() resolves `--set {slug}` to either form, preferring
folder when both exist and warning on stderr about the conflict.
- resolve_active_entity_path / load_active_entity_fields preserve the
entity's relative location inside the worktree so folder entities map
to `{worktree}/{slug}/index.md` rather than `{worktree}/index.md`.
- run_archive() handles folder entities: stamps `archived:` into the
inner `index.md`, then moves the whole folder into `_archive/{slug}/`.
Flat-file archival is byte-for-byte unchanged.
- Header docstring documents the new discovery, conflict, and archive
behavior.
Tests:
- New TestEntityAsFolder suite covers mixed / folder-only workflows,
`--set` / `--archive` on folder entities, the conflict warning, and
reserved-dir exclusions. Existing 138-case status-script suite keeps
passing unchanged.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…ity naming
Extend the File Naming section so workflows commissioned after this
change know both forms are first-class: flat `{slug}.md` (default) or
folder `{slug}/index.md` (when the entity produces per-stage artifacts
alongside the tracker).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
b4457f4 to
784ccf6
Compare
clkao
added a commit
that referenced
this pull request
Apr 20, 2026
clkao
added a commit
that referenced
this pull request
Apr 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #99.
Motivation
Hit this again on the release workflow — v1-43-0 is ready to archive but
status --set / --archive can't resolve
v1-43-0/index.md. Every folder-basedworkflow (blog-writing, release, future commissions) trips the same
non-recursive scan at the first archive boundary.
Change
{slug}/index.mdwhen the flat{slug}.mdis absentstatus --setresolves folder entities by the same rulestatus --archivestampsarchived:in the inner index and moves the whole folder to_archive/{slug}/--archived,--boot,--next,--next-id,--whereall inherit via shared discovery_archive,_mods) are excluded from entity detectionTest
🤖 Generated with Claude Code