Skip to content

Bucket list: add :regex() at name_one for RESULTS - #277

Open
dk107dk wants to merge 18 commits into
mainfrom
docs/regex-name-one-results-bucket-item
Open

dk107dk wants to merge 18 commits into
mainfrom
docs/regex-name-one-results-bucket-item

Conversation

@dk107dk

@dk107dk dk107dk commented Aug 29, 2026

Copy link
Copy Markdown
Collaborator

Docs only. Adds a bucket-list entry for :regex() as a name_one selector for RESULTS (matching a run's own directory name by pattern, at any template depth) -- confirmed unsupported today (:regex() is not legal at name_one for results), surfaced while reading worked examples for the :home()/:all() investigation. No code changed.

https://claude.ai/code/session_013gPjejPWvbWtjz2dw9h14M

David Kershaw and others added 18 commits August 29, 2026 14:22
Surfaced while working through :home()/:all() worked examples --
$alpha.results.:regex("2026-01-01_").header_checks:errors() (matching a
run's own directory name by pattern, at any template depth) does not
parse today, confirmed live. Distinct from :regex() at root_major
(matches group names, already built) -- this would match run names
instead, orthogonal to the :home()/:all() template-depth selectors.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013gPjejPWvbWtjz2dw9h14M
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