Install
This is the repository archive. It installs, but the folder name will carry the branch suffix and updates will not flow.
Install straight from GitHub with WP-CLI:
wp plugin install https://github.com/majidhussainqadri1-dot/04-sabri-news-feed-and-publishing/archive/refs/heads/main.zipFile 04 — News Feed and Publishing — Legacy Foundation Adapter v2.0.8
File 04 remains a temporary, write-disabled, auditable and reversible migration/compatibility adapter. File 21 is the sole canonical publication/Home/News/feed owner; File 26 owns search/discovery; File 20 owns the shell; File 25 owns the visual system; File 24 coordinates assurance. File 04 does not create a second composer, feed, ranking service, comments/reactions store, moderation backend, search engine or permanent public route system.
Governing scope
The source trace covers the consolidated governing plan, File 04 FR-001..013 and NFR-001..010, 71 CV requirements (all applicable central requirements), F04-CEN-01..02, 15 acceptance journeys and F04-FUT-001..018.
v2.0.8 current exact-head correction
The v2.0.8 candidate corrects defects found after re-freezing the current File04 and companion heads: REST inventory capture now persists the signed lock and lifecycle transition; REST dry-run binds its bounded limit and lifecycle arguments correctly; the status API uses a validated privacy-minimized inventory summary; File21 receives and verifies all governed legacy metadata plus explicit child/featured media relations; and File23 receives bounded read-only migration diagnostics. CI now checks the exact current heads of Files 00, 01, 17, 19, 20, 21, 22, 23, 24, 25, 26 and CF-04.
v2.0.7 exact companion-parity completion
The historical v2.0.6 line completed the second 80-round File04 source audit. A later fresh 20-pass review compared File04 to the current exact companion repositories; v2.0.7 adds the resulting parity corrections:
- strict canonical File26 legacy-ID validation with no negative/malformed aliasing;
- explicit operator-authorized File01 module/route registration and a File20 route-context contract;
- File19 producer registration plus
LegacyMigrationBatchCompleted.v1,LegacyRecordQuarantined.v1,LegacyCutoverCompleted.v1andLegacyAdapterRetired.v1event emission; - File24 module assurance manifest/state integration while preserving native File04 controls;
- privileged read-only System Check/metrics access during a File21 outage without permitting migration writes;
- correction of the File04 plan REST namespace to
SNFLA_REST::NS; - strict retirement actor/lifecycle-version semantics;
- removal of completed one-time R80 helper workflow/scripts and permanent deterministic regression coverage;
- current File00 identity/author-placeholder interoperability, canonical File01 route syntax, File20
system_recoverycontext, File21 author/media migration interoperability, complete File24 manifest fields, and File26 cutover/reindex compatibility; COMPANION-CONTRACT-LOCK.jsonplus an exact frozen-companion CI parity gate.
Storage schema remains 1.3.0 because these corrections do not change custom-table structure.
Truthful lifecycle status
Repository/source correction, deterministic packaging, exact-head CI, Hostinger staging acceptance, live deployment and sustained operations are separate states. This repository must not claim production readiness from source code alone. Real File00/File01/File19/File20/File21/File24/File25/File26 integration evidence, representative legacy data, browser/WCAG/RTL acceptance, backup/isolated restore, rollback/DR rehearsal, Founder approval and production monitoring remain external gates.