Rename gherkinize template and tag config files

[CleanDev-Fix]

Summary

• rename tools/gherkin.feature.jinja to tools/gherkinize.feature.jinja
• rename tools/wip.toml to tools/tags.toml
• update the tool references and docs/notebook references to use the new names

Notes

This keeps the change scoped to the file naming cleanup discussed in #171. The broader JSON/TOML output redesign mentioned in the issue is intentionally left for a separate follow-up.

Testing

.\.venv\Scripts\python.exe -m pytest -q tools
......                                                                   [100%]
6 passed in 0.11s

Fixes #171

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: Nbluff / name: CleanFixDev (2bc1ef3)

[slott56]

Very nice. I was hoping to drop the .jinja from the template file so the name had an extension of .feature.

For testing, look at the Makefile. It can run a variety of tests. If you use the bare make command it should provide documentation on all the alternative targets.

[CleanDev-Fix]

Updated the follow-up requested in review.

Changes:

• Renamed tools/gherkinize.feature.jinja to tools/gherkinize.feature
• Updated the Jinja loader reference
• Updated the tools README reference

Verification:

• make runs and shows the repo targets.
• make test-tools passes: 6 passed.
• make test runs through the Makefile/tox path on Windows, but hits an unrelated platform-specific failure in tests/test_main.py::test_stat_good because os.getegid is not available on Windows. The tools tests covering this change pass locally, and GitHub CI can cover the normal project matrix.

[slott56]

Interesting. Custodian never runs in a Windows context, but CEL-Python could be run that way. That's a totally unrelated issue exposed by this. Very helpful.

[slott56]

Outstanding! Very helpful. Very quick, too.