breaking change: a third project type, and the README rules only a render reveals

[obarlik]

Two changes, one per commit.

A third project type. The existing two assume something ships: a
library installed by other software, or an application opened by a
person. A repo carrying a method, the pipeline that runs it, and an
honest verdict about whether it works is neither. Forcing it into the
library skeleton makes the README promise things it cannot keep — a
five-line quick example when there is nothing to install, a family
table when there is no registry namespace. RESEARCH-LINE.md names
those two bullets inapplicable, says what replaces them, and keeps
every other vitrine rule.

Rendering rules in §7.1. Five things were true of our READMEs for
as long as they had been written and none were visible in the markdown
source: the README is not the fold (~1080 px down, under the file list
and About box — so description and topics, which are settings and not
files, are the most-read text); two blockquote lines collapse into one;
a dead badge still looks like a signal; a fence clips rather than
wraps; an indented block gets no highlighting. Found by rendering
through gh api /markdown and looking. They are properties of GitHub,
so they sit in §7.1, not in one project type.

Ripple: every product repo's README is now measured against §7.1's
rendering rules. Nothing existing becomes invalid — the two annotated
bullets are narrowed, not removed.

TR mirror updated for both. Known gap, not addressed here:
STANDARDS.tr.md has no §13 "Layered conventions" section at all
(its §13 is "Aktif repolar"), so the layer-table row has no TR home.

[Copilot]

Pull request overview

Adds a third project type (“research line”) to Codechu’s project taxonomy and updates README “vitrine” standards with GitHub-rendering-specific rules that only become apparent when viewing the rendered README.

Changes:

• Introduces project-type/RESEARCH-LINE.md defining language-agnostic conventions for “research line” repositories and clarifying which §7.1 README bullets do not apply.
• Extends STANDARDS §7.1 (EN + TR) with measured GitHub rendering rules (fold location, blockquote line collapse, dead badges, code-fence clipping, and indented-block highlighting).
• Updates the project-type index/table and layered-conventions text to include “research line” alongside library and application.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated no comments.

File	Description
STANDARDS.md	Adds research-line exceptions to two README vitrine bullets; adds measured GitHub rendering rules; updates layered conventions to include research lines.
STANDARDS.tr.md	Turkish mirror: adds research-line exceptions and the measured GitHub rendering rules in §7.1.
project-type/RESEARCH-LINE.md	New project-type spec describing research-line repos, README skeleton, and measurement-derived presentation rules.
project-type/README.md	Adds “Research line” to the project-type matrix and directory tree; updates intro text to reflect >2 types.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.