Engineering Intelligence Framework v0.2.3

A scope correction, not a code change. Nothing about how EIF behaves is
different in this release.

What was removed

docs/product/linkedin-series.md held an audience definition, voice rules,
commenting rules, and the arc of a publication series. None of that
describes EIF. It describes a marketing practice, and a framework repository
that documents its own marketing practice is slowly becoming its marketing.

It moved to the maintainer's private communications repository, where the
drafts, the reaction data, and the named third-party threads it governed
already lived.

What stayed, and why the line falls there

The claims register is unchanged and stays public. It is the
machine-enforced half: the site build fails when a page states something the
register does not allow, and a bound nobody can verify is not a bound.
Publishing it is the mechanism rather than a gesture, and each entry names
the evidence for a capability, which is genuinely about the framework.

The test for anything else: if it describes EIF or the evidence for a claim
about EIF, it belongs here. If it describes a person we are trying to reach,
or how to reach them, it does not.

Also in this release

docs/README.md and ROADMAP.md no longer enumerate publication channels.
The claims register's preamble now says "any public copy about EIF, wherever
it appears" instead of listing surfaces, which is what it always meant.

Historical CHANGELOG entries keep their text and lose the dead link.
Rewriting history to hide that the file existed would be worse than a note
saying where it went.

Known limitations

Unchanged from 0.2.2, including the three installed-wheel
integration-status checks in scripts/tests/test_package_build.py that fail
identically on 0.2.0 through 0.2.3. Not a regression, not fixed here. The
package is still distributed through GitHub Releases rather than PyPI.

Install

python -m pip install ./engineering_intelligence_framework-0.2.3-py3-none-any.whl
eifctl version