mirror of
https://github.com/kuhyx/WUT_Computer_Science.git
synced 2026-11-10 22:07:10 +01:00
Krzysztof kuhy Rudnicki
54337a662e
Five files were outside README / CLAUDE* / DOCS* / TODO*, and two were over the 250-line cap. Both gates now pass repo-wide. Renames: the two lowercase readme.md files, and three documents into DOCS-*. The AIS requirements doc split at its own boundary into functional (101) and non-functional (174). The WDWR report split into six numbered sections behind an index that keeps the original filename, 38-235 lines each; 753 lines of body plus the 18-line header account for all 771 original lines, so nothing was dropped. That WDWR file needed checking before splitting: it sits next to main.tex and main.pdf and looked like a conversion of them. It is not -- main.tex is project 25406 and the markdown is project 18402, a different document. So it is authored content and the split is real work, not churn on a build artifact. Filled the three empty READMEs and replaced ECOTE's, which was a stale copy of the root README still claiming the group projects were excluded -- they were merged in by subtree some time ago. EOPSY/lab1 turned out not to be the code-free directory the survey suggested: it has modify.sh and modify_examples.sh. The oddly-named empty files beside them are the exercise's OUTPUT, committed so the before/after state is visible, and its README now says so rather than leaving them looking like junk. CLAUDE.md follows the testsAndMisc structure. Writing it caught a nice one: the md-naming marker is a biconditional, so quoting the literal removal string in a non-TODO file fails the gate. The gate was right; the text is rephrased. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0172dj34FDpao6wsix8ZuCzE
15 lines
603 B
Markdown
15 lines
603 B
Markdown
# EOPSY — lab 1: shell scripting
|
|
|
|
A shell-scripting exercise: recursively rename files and directories to
|
|
lower case, and drive `sed` over a tree.
|
|
|
|
| Path | What it is |
|
|
|---|---|
|
|
| `modify.sh` | The submitted solution. |
|
|
| `modify_examples.sh` | Worked examples used while developing it. |
|
|
| `A`, `b`, `RECURSEFILE`, `sed`, `recurselowerfile`, `LOWERCASEFOLDERMAIN`, ... | Fixture and result files. |
|
|
|
|
The oddly-named empty files are not junk and are not source: they are the
|
|
*output* of running the scripts, committed so the before/after state of the
|
|
exercise is visible. Their names are the point.
|