Stale release and install facts
README pins and Go requirements drifted from source. Use current build files and scoped follow-up tickets; a story snapshot is not a release guarantee.
Site review: · Dated evidence and limits
Hygiene findings
Why
Keep the site grounded in the actual source state. The portfolio review filed follow-up issues instead of quietly turning known gaps into product claims.
These are findings from 2026-10-04, not a claim that every upstream issue remains open or has since been fixed. This website pass does not repair other repositories.
Local dependency resolution
Machine-local replace directives can make a public checkout fail. Test published module resolution independently of sibling workspaces.
Missing entry points
A useful implementation can still lack a root overview or public install path. Record that gap instead of inventing a finished product page.
Checks that do not execute tests
A successful make target can conceal a non-running test suite. Verify the command and result rather than treating its name as evidence.
Tracker formats and stale closure claims
Custom tracker indexes impeded automation; closed checklists sometimes disagreed with implementation. Reconcile the actual outcome before site claims.
Private identifiers in reusable material
Device identifiers and host-specific reports need source review. A clean summary does not certify every linked upstream document as sanitized.
Product claims ahead of implementation
Wayreel records scripted demos, but automatic README updates depend on user-configured integration. Link the correction rather than repeating the promise.