Steps to Reproduce
- On a site with plan content in a git repository, add
{% plan-history since="1d" /%}. - Add
{% plan-history group="entity" /%} beside it. - Build the site.
Expected
The first feed shows only events from the last day. The second groups events by entity.
Actual
Both render the same unfiltered, commit-grouped feed as {% plan-history /%}, with no warning.
Environment
@refrakt-md/plan at the current main.
Resolution options
SPEC-172 records the direction for repository history in general, and questions whether plan-history survives as its own rune. Either option fixes the bug:
- Implement both.
since filters by event date (7d, 30d or an ISO date, as documented); group="entity" groups the global feed by entity instead of by commit. - Remove both from the schema and the documentation, so the rune stops promising what it does not do.
Removing them is the smaller change while the rune's future is open. Leaving the attributes in place and doing nothing is the one outcome this bug rules out.