Thirteen-Post NSVault Blog Backfill Design

Status

Approved by the user on 18 July 2026. The user approved replacing the overlapping 9 July Home Team ORNS topic with the SPF PNS OCC topic on 19 July 2026 after production published the general Home Team guide.

This document defines a one-time manual backfill for the 13 calendar dates that have no NSVault blog publication between 11 May 2026 and 18 July 2026. It does not change the LearnNet Blog Automation's normal daily cadence.

Problem

The production repository and live sitemap are currently in sync, but the publication calendar has 13 empty dates:

• 2026-05-11
• 2026-06-25
• 2026-06-26
• 2026-06-27
• 2026-06-28
• 2026-06-29
• 2026-06-30
• 2026-07-01
• 2026-07-05
• 2026-07-09
• 2026-07-12
• 2026-07-17
• 2026-07-18

The audit found no completed local-only post waiting to be pushed. A 9 July run left two untracked images and an empty post directory for an intern reservist make-up-pay article, but that topic is now covered by the student and intern pay guides. Those leftovers are unrelated user files and must not be staged, deleted, reused, or overwritten.

The backfill therefore needs genuinely useful new coverage. It cannot be a set of thin rewrites created only to fill dates.

Goals

• Publish one distinct, substantial NSVault post for each missing date.
• Base every policy, benefit, pay, medical, employment, eligibility, and admin statement on current official or primary guidance checked on 18 July 2026.
• Use recent Singapore NS Reddit discussions only as evidence of reader demand.
• Avoid cannibalising existing posts, especially recent posts from May to July.
• Produce an original 1400x788 PNG and WebP hero for every post.
• Pass the complete repository test and production build before publishing.
• Push the verified batch normally to the production branch resolved from origin/HEAD.
• Leave the daily automation configured to publish at most one post per future run.

Non-Goals

• Reconstructing or publishing the abandoned 9 July intern MUP draft.
• Rewriting existing pages to manufacture new slugs.
• Publishing seven posts per weekly automation run.
• Changing blog components, routing, Docusaurus configuration, or production application code.
• Giving medical or legal advice, predicting PES or promotion outcomes, or advising readers to avoid NS obligations.
• Quoting Reddit users, naming Reddit users, or turning personal Reddit cases into stories.
• Using Vercel CLI or API.

Delivery Model

This is a user-approved manual exception to the automation's one-post-per-run limit. The implementation will create all 13 historical posts in one batch and publish them together after full verification.

Each post will use:

• a folder named blog/YYYY-MM-DD-<slug>/;
• an explicit frontmatter timestamp on the assigned historical date;
• a timestamp of 09:00:00+08:00, because the missing dates are Singapore publication slots and none conflicts with another post on the same date;
• an immutable, unique frontmatter slug;
• images at static/img/blog/<slug>.png and static/img/blog/<slug>.webp.

No existing post or image will be overwritten. If any proposed folder, slug, or image path exists when implementation begins, the overlap check must stop the batch before writing.

Implementation will happen in a clean worktree based on the latest production branch. The original workspace's unrelated untracked outreach report and abandoned 9 July images will remain untouched.

Shared Article Contract

Every post must follow the current NSVault MDX pattern:

1. Frontmatter with slug, date, title, description, keywords, image, authors, and block-style tags.
2. A 30-60 character effective title.
3. A 110-170 character description.
4. At least five unique keywords and at least four useful tags.
5. Imports for BlogHero and BlogFaq.
6. A direct introduction that states the reader problem and NSVault's unofficial status.
7. A custom BlogHero using both new image files and accurate alt text.
8. <!-- truncate --> immediately after the opening experience.
9. A Quick version details block.
10. A clear applicability section.
11. Practical sections organised around decisions, records, dates, and official channels rather than generic background.
12. A common-mistakes section where it helps the reader avoid a real error.
13. Exactly three useful FAQ items rendered with BlogFaq.
14. An Official References section containing only sources actually used.
15. A concise bottom line.
16. Three to five verified Related Reads links to existing NSVault routes.

Articles should normally land between 1,100 and 1,800 words. A narrower post may be shorter only if it still answers the complete reader job. Padding is not a substitute for useful coverage.

Reddit links belong in research records and the final run report, not in the public article. Articles must not quote, attribute, screenshot, or retell a Reddit user's personal circumstances.

Accuracy Contract

• Official instructions, account records, call-up notices, unit directions, and written agency replies override every post.
• Public uncertainty must remain visible. If an official page does not publish a personal timeline, selection probability, approval threshold, or unit procedure, the article must say so.
• A more recent and more authoritative primary source wins when sources conflict.
• Facts that cannot be verified are omitted.
• Medical posts explain records and official routes, not diagnoses or likely outcomes.
• Employment content explains official protections and escalation channels but is not legal advice.
• Equipment content never recommends buying controlled equipment secondhand or bypassing unit accountability.
• The relationship and hygiene posts use official sources only for NS-specific facts. Their practical advice must be framed as options, not official rules.
• Each post should state that its official public sources were checked on 18 July 2026, so the historical publication slot is not mistaken for the source-verification date.

Topic Scoring

Each topic is scored from 1 to 5 on:

• D: Reddit demand
• G: NSVault coverage gap
• O: official-source strength
• E: evergreen usefulness
• C: factual clarity, where 5 means low ambiguity

Date	Topic	D	G	O	E	C	Total
2026-05-11	SkillsFuture@NS LXP	4	5	5	5	5	24
2026-06-25	Verify MINDEF contacts	4	5	5	5	5	24
2026-06-26	NS insurance vs service injury	4	5	5	5	4	23
2026-06-27	EEDS civilian expertise	3	5	5	4	4	21
2026-06-28	Relationships during NS	5	5	2	5	3	20
2026-06-29	Mono-intake BMT	5	5	4	5	4	23
2026-06-30	DIS DigiSpec	4	5	5	4	4	22
2026-07-01	SPF and SCDF ranks and allowance	3	5	5	5	4	22
2026-07-05	Missing or old SAF gear before ICT	5	5	4	5	4	23
2026-07-09	SPF PNS OCC after POBC	4	5	5	4	4	22
2026-07-12	Bunk hygiene and shared living	3	5	4	4	4	20
2026-07-17	NS employment rights	4	5	5	5	4	23
2026-07-18	SAF Card after ORD	2	5	5	5	4	21

Approved Portfolio

1. SkillsFuture@NS LXP: Access and Course Guide

• Date: 2026-05-11
• Slug: skillsfuture-ns-lxp-access-course-guide
• Reader job: Understand the current programme, activate access, plan the two-year access window, and avoid relying on obsolete e-PREP advice.
• Demand: SkillsFuture@NS programme discussion
• Official anchors: MINDEF 2022 fact sheet and MINDEF 2024 update.
• Coverage gap: Existing benefits and ORD pages mention credits and preparation but do not explain the SkillsFuture@NS Learning eXperience Platform.
• Required boundary: Explain that SkillsFuture@NS LXP replaced e-PREP. Do not promise a particular course, certificate, provider, activation date, or career outcome.
• Internal-link cluster: /blog/nsf-benefits-claims-checklist, /blog/ord-preparation-checklist, /blog/a-guide-to-your-ns-lifesg-credits, and /docs/nsf-start-here.
• Hero concept: A neutral learning desk with an abstract course grid, notebook, headphones, and calendar. No readable screen text or platform branding.

2. How to Verify a MINDEF Call, SMS or Email

• Date: 2026-06-25
• Slug: verify-mindef-call-sms-email-scam-guide
• Reader job: Verify a missed call or message without exposing Singpass, OTP, bank, or personal information.
• Demand: Missed MINDEF call discussion.
• Official anchors: MINDEF scam guidance, official MINDEF contact routes, and ScamShield guidance.
• Coverage gap: NSVault has SAF100 and portal guides but no verification workflow for unexpected MINDEF communications.
• Required boundary: Do not publish a guessed list of trusted phone numbers. Teach readers to start from an independently opened official site or portal.
• Internal-link cluster: /blog/saf100-acknowledgement, /blog/missed-ict-no-saf100, /blog/ns-registration-documentation, and /docs/nsmen-start-here.
• Hero concept: A generic phone with an abstract incoming-call panel, a verification shield, and a notebook. No phone number, logo, or readable message.

3. NS Insurance vs Service Injury Claims

• Date: 2026-06-26
• Slug: ns-insurance-vs-service-injury-claims-guide
• Reader job: Separate group insurance, service-injury recognition, treatment subsidy, service injury cards, and compensation.
• Demand: Recent injury-after-NSF discussion and recurring questions about the difference between insurance and service injury.
• Official anchors: SAF insurance and service injury and SCDF insurance and service injury.
• Coverage gap: Existing pages focus on reporting and follow-up for service injury. They do not provide a lane-by-lane comparison of insurance, recognition, subsidy, and compensation.
• Required boundary: Never predict whether an incident will be accepted or what compensation will be paid. Tell readers to report promptly and preserve official and medical records.
• Internal-link cluster: /blog/service-injury-after-ord, /blog/service-injury-medical-review-guide, /blog/nsf-medical-dental-claims, and /blog/nsmen-transport-and-medical-claims.
• Hero concept: Two clearly separated but unlabeled document paths beside a medical folder and protective cover motif. No policy text or official marks.

4. EEDS: Using Civilian Expertise During ORNS

• Date: 2026-06-27
• Slug: eeds-civilian-expertise-orns-guide
• Reader job: Decide whether and how to register civilian expertise for operationally ready service.
• Demand: AskSingapore EEDS discussion, NationalServiceSG EEDS discussion, and recent expertise-deployment discussion.
• Official anchors: MINDEF March 2026 parliamentary reply, MINDEF February 2026 fact sheet, and Enhancing NS.
• Coverage gap: NSVault has no dedicated guide to the Expertise-based Deployment Scheme.
• Required boundary: Registration is not a redeployment promise. Selection depends on suitability and operational need, and public guidance does not publish a personal success probability or timeline.
• Internal-link cluster: /blog/first-ict-after-ord-checklist, /blog/sign-on-during-ns-regular-service, /blog/makeup-pay-for-nsmen-explained, and /docs/nsmen-start-here.
• Hero concept: A civilian skills desk with digital, counselling, legal, and planning objects converging on an ORNS calendar. Avoid insignia and readable profession labels.

5. Relationships During NS: A Practical Plan

• Date: 2026-06-28
• Slug: relationships-during-ns-practical-plan
• Reader job: Build a sustainable communication and recovery plan when NS fatigue and changing schedules reduce shared time.
• Demand: June 2026 relationship discussion.
• Official anchors: CMPB pages on taking leave, family emergency contacts, living in camp, and where to seek help.
• Coverage gap: Existing pages cover leave, family emergencies, loneliness, and mental-health support separately. None addresses the relationship-planning job.
• Required boundary: Do not promise contact frequency, nightly phone access, weekend book-out, block leave, or a fixed training schedule. Do not present relationship advice as therapy.
• Internal-link cluster: /blog/mental-health-help-in-ns, /blog/bmt-family-emergency-contact-guide, /blog/annual-leave-after-pop-bmt-guide, and /blog/lonely-in-bmt-first-week-guide.
• Hero concept: Two mugs, a shared calendar, a charging phone, and a small stack of simple date ideas. No identifiable people or readable messages.

6. Mono-Intake BMT: What It Actually Means

• Date: 2026-06-29
• Slug: mono-intake-bmt-what-it-means-guide
• Reader job: Understand what mono-intake changes and what cannot be known before official enlistment and posting information arrives.
• Demand: July mono-intake questions, mono-intake confinement discussion, and mono versus non-mono discussion.
• Official anchors: MINDEF 2018 speech, MINDEF AskGov mono-intake answer, and CMPB Basic Military Training.
• Coverage gap: BMT programme and confinement pages do not explain mono-intake as a unit-cohesion model.
• Required boundary: Do not predict a future unit, intake date, posting, or training detail from Reddit rumours.
• Internal-link cluster: /blog/bmt-programme-1-2-3, /blog/bmt-confinement-and-first-book-out-guide, /blog/bmt-items-issued-what-to-buy, and /blog/what-to-expect-in-your-first-week-after-posting-out-of-bmt.
• Hero concept: A set of recruits represented by neutral geometric kit layouts moving together from a training block to a unit block. No people, uniforms, crests, or unit markings.

7. DIS DigiSpec Work-Learn Scheme Guide

• Date: 2026-06-30
• Slug: dis-digispec-work-learn-scheme-guide
• Reader job: Evaluate eligibility, selection, study path, contract, and service commitment before applying.
• Demand: June 2026 DigiSpec discussion.
• Official anchor: DIS DigiSpec Work-Learn Scheme, including the current application and partner-institution information linked from that page.
• Coverage gap: The general signing-on guide covers broad regular pathways, not DigiSpec's specific four-year work-learn structure.
• Required boundary: Do not guarantee admission, posting, institution, qualification outcome, or a future application window. Quote no applicant anecdotes.
• Internal-link cluster: /blog/sign-on-during-ns-regular-service, /blog/command-school-after-bmt, /blog/ns-transcript-testimonial-ord-guide, and /docs/nsf-start-here.
• Hero concept: A digital study desk with code-like abstract blocks, textbooks, a calendar, and hardware tools. No readable code, DIS mark, or uniformed figure.

8. SPF and SCDF NSF Ranks and Allowance Guide

• Date: 2026-07-01
• Slug: spf-scdf-nsf-ranks-allowance-guide
• Reader job: Decode Home Team hierarchy and distinguish rank, vocation, and meal allowance components.
• Demand: June 2026 enlistment megathread and recurring Home Team promotion questions.
• Official anchors: SPF ranks, SPF allowance, SCDF ranks, and SCDF allowance.
• Coverage gap: NSVault's rank guide is SAF-specific. The existing SPF and SCDF training guides do not explain the Home Team allowance structure.
• Required boundary: Do not infer promotion timing or entitlement from anecdotes. Allowance tables must be rechecked immediately before writing.
• Internal-link cluster: /blog/saf-ranks-chain-of-command-first-week-guide, /blog/spf-pobc-enlistment-day-guide, /blog/scdf-nstc-enlistment-day-guide, and /blog/nsf-allowance-and-payslip-explained.
• Hero concept: Two neutral rank-ladder paths with abstract shoulder tabs, coins, and a calendar. Do not reproduce official insignia.

9. Missing SAF Gear Before ICT: What to Do

• Date: 2026-07-05
• Slug: missing-old-saf-gear-before-ict-guide
• Reader job: Audit issued equipment, replace ordinary eMart items, and ask the unit about missing or controlled items before reporting.
• Demand: July 2026 old-kit ICT discussion and reservist after a long gap.
• Official anchors: Current MINDEF AskGov guidance on eSAF100 instructions, eMart credits and active status, unit-specific full battle order, mobilisation items, and disposal of old equipment.
• Coverage gap: The ICT packing and eMart pages do not give a staged response for missing issued or controlled equipment.
• Required boundary: The public sources do not decide accountability for a particular missing item. Never advise buying controlled equipment from unofficial sellers or concealing a loss.
• Internal-link cluster: /blog/ict-packing-list-for-nsmen, /blog/first-ict-after-ord-checklist, /blog/a-guide-to-using-your-saf-emart-credits, and /blog/missed-ict-no-saf100.
• Hero concept: Worn boots, a field bag, an abstract inventory checklist, and an eMart parcel arranged on a neutral bench. No weapon, insignia, readable list, or real uniform.

10. SPF PNS OCC After POBC: Selection Guide

• Date: 2026-07-09
• Slug: spf-pns-occ-after-pobc-selection-guide
• Reader job: Understand the official PNS OCC route after POBC, what public guidance says selection is based on, what the 32-week residential course leads to, and what it does not promise after a trainee misses initial selection.
• Demand: Post-POBC SPF OCC question.
• Official anchors: CMPB after basic training.
• Coverage gap: The existing POBC article focuses on enlistment and basic training, while the command-school article is SAF-specific. Production commit e44fdaf now owns the general Home Team reservist call-up intent. No existing article explains the SPF PNS OCC selection route and its public limits.
• Required boundary: CMPB says strong POBC performance and demonstrated leadership potential lead to PNS OCC selection. It does not publish a cutoff, selection probability, appeal process, or guaranteed later crossover route. Direct case-specific questions to Training Command or the trainee's unit through official channels.
• Internal-link cluster: /blog/spf-pobc-enlistment-day-guide, /blog/what-determines-your-vocation, /blog/command-school-after-bmt, /blog/a-guide-to-ns-vocations, and /blog/spf-scdf-nsf-ranks-allowance-guide.
• Hero concept: A blank training notebook, stopwatch, route markers, and an unreadable course board in a neutral indoor academy setting. No people, uniforms, police insignia, logos, readable text, or official interface.

11. Bunk Hygiene Problems: A Practical NS Guide

• Date: 2026-07-12
• Slug: bunk-hygiene-shared-living-ns-guide
• Reader job: Handle repeated hygiene and shared-space problems with a proportionate sequence of direct conversation, shared standards, commander support, and medical attention when symptoms exist.
• Demand: July 2026 bunk hygiene discussion.
• Official anchors: SAF living in camp, SPF living in HTA, SCDF living in NSTC, and official help channels.
• Coverage gap: Packing and first-week posts discuss personal preparation, but none provides a conflict-safe process for ongoing communal hygiene issues.
• Required boundary: Do not diagnose infection, prescribe treatment, encourage public shaming, or promise disciplinary outcomes.
• Internal-link cluster: /blog/report-sick-in-camp-without-the-admin-mess, /blog/mental-health-help-in-ns, /blog/bmt-packing-list-the-ultimate-guide, and /blog/lonely-in-bmt-first-week-guide.
• Hero concept: A clean shared bunk layout with toiletries, laundry bag, ventilation, and a simple chore board with no readable text. No people or official barracks markings.

12. NS Employment Rights for Reservist Call-Ups

• Date: 2026-07-17
• Slug: ns-employment-rights-reservist-call-ups-guide
• Reader job: Distinguish fair hiring, employer notice, protected NS leave, dismissal protection, pay handling, and ICT deferment.
• Demand: Recent rejected-deferment and employer discussion, probation and ICT discussion, and when to tell an employer.
• Official anchors: MINDEF employment-rights guidance, TAFEP fair-employment guidelines, and the MINDEF employer handbook.
• Coverage gap: Existing employer and MUP guides explain payroll and claims. Deferment guides explain requests to the unit. None owns the employment-rights decision tree.
• Required boundary: This is not legal advice. Do not imply that employment protection guarantees deferment, a hiring outcome, or a particular remedy.
• Internal-link cluster: /blog/employer-guide-to-ict-and-make-up-pay, /blog/makeup-pay-for-nsmen-explained, /blog/ict-deferment-and-rescheduling-guide, and /blog/ict-deferment-supporting-documents.
• Hero concept: A work calendar, briefcase, laptop, and abstract recall notice aligned on one desk. No company logos, readable legal text, or official form.

13. SAF Card After ORD: Keep, Update or Return?

• Date: 2026-07-18
• Slug: saf-card-after-ord-keep-update-return-guide
• Reader job: Know whether the card remains valid, when the NSman status sticker matters, who returns a card, and how an NSman replaces a lost card.
• Demand: ORD sticker question and first ICT after a long gap.
• Official anchors: SAF Card validity, returning the SAF Card, and lost-card handling.
• Coverage gap: The existing lost-11B page owns detailed loss and replacement steps. No page explains the keep, update, or return decision at ORD.
• Required boundary: Do not conflate the physical SAF Card with OneNS Wallet or general Singpass digital identity. Keep lost-card detail concise and link to the existing replacement guide.
• Internal-link cluster: /blog/lost-saf-11b-replacement, /blog/ord-preparation-checklist, /blog/first-ict-after-ord-checklist, and /blog/ns-transcript-testimonial-ord-guide.
• Hero concept: A generic, non-official identity card silhouette with a small status tab, ORD calendar, and storage folder. No portrait, number, logo, or readable text.

Image System

The batch will create exactly 26 final image files:

• 13 PNG files
• 13 WebP files

Every pair must:

• be original and visually distinct;
• render at exactly 1400x788 pixels;
• match the quiet editorial style of recent NSVault heroes;
• use neutral materials with topic-specific accent colours so the set does not become a one-hue series;
• avoid logos, badges, official insignia, real uniforms, weapons, official app screenshots, readable documents, identifiable people, and implied government endorsement;
• use the same composition in PNG and WebP;
• accurately match the article's alt text;
• keep WebP below 400 KB when quality remains acceptable;
• keep PNG reasonably compressed without visible damage.

Generation output, raw intermediates, prompts, screenshots, and temporary conversion files must remain outside the repository and be deleted from the clean worktree before staging.

Repository Changes

The content implementation commit is expected to contain:

• 13 new blog/YYYY-MM-DD-<slug>/index.md files;
• 13 new static/img/blog/<slug>.png files;
• 13 new static/img/blog/<slug>.webp files;
• one focused update to tests/tool-rendered-html.test.mjs.

The rendered-blog-index test has hard-coded expected card order. Inserting historical dates changes pagination boundaries, so the expected arrays must be updated to the order produced by the intended frontmatter dates. No other test or application code should change.

This design document is committed separately from the implementation commit.

Verification

Preflight

1. Run git fetch origin.
2. Resolve the production branch using git symbolic-ref refs/remotes/origin/HEAD.
3. Confirm no other production-push automation run is active.
4. Create a clean worktree from the latest production branch plus this approved specification.
5. Confirm all 39 proposed content and image paths are absent.
6. Re-run the slug and title overlap audit across all existing blog posts.
7. Re-open every official source used for a factual claim.

Content and asset checks

1. Confirm exactly 13 new Markdown files and 26 new image files.
2. Validate frontmatter parsing, title length, description length, unique keywords, block tags, image path, and author.
3. Confirm every post imports and uses both BlogHero and BlogFaq.
4. Confirm every post has one truncate marker, one quick-version block, three FAQ items, official references, and three to five valid internal links.
5. Confirm all 26 images render and are exactly 1400x788.
6. Record PNG and WebP byte sizes.
7. Check official external links with a normal GET where practical. A bot block is recorded separately from a genuine broken link.
8. Scan for Reddit usernames, copied phrases, fabricated anecdotes, unverified amounts, unsupported timelines, and instructions that could evade NS duties.

Repository checks

Run:

1. npm ci only if dependencies are missing.
2. npm test.
3. npm run build.
4. git diff --check.

Then inspect:

• rendered /blog pagination and each of the 13 article routes;
• generated metadata, canonical URLs, images, FAQ rendering, and related links;
• git diff --stat and git status;
• absence of build/, .docusaurus/, caches, notes, screenshots, downloads, prompts, raw images, queue state, and automation memory from the staged diff.

The implementation commit may contain only the 39 post/image files and the one expected rendered-order test update.

Commit and Production Integration

1. Stage only the approved implementation files.
2. Commit with the repository's required conventional format, for example: docs(feat): backfill thirteen verified NS guides.
3. Fetch the latest production branch again.
4. If production moved, rebase normally, rerun overlap checks, tests, build, link checks, and diff checks.
5. Push normally to the resolved production branch.
6. Never force-push or rewrite published history.
7. Verify the pushed commit is reachable from origin/<production-branch>.
8. Without Vercel CLI or API, retry each live /blog/<slug> URL after the git integration has had time to deploy.
9. Confirm all 13 slugs appear in the live blog sitemap and return successful article pages.
10. Update the original workspace from production only when it can be done without disturbing unrelated untracked files.

Automation State

After production verification:

• update the external weekly topic queue to mark matching ideas as published or superseded;
• do not place the queue file in the repository;
• update automation memory with the 13 dates, slugs, demand URLs, official verification result, test and build result, image size summary, commit hash, push result, live URL results, skipped duplicate topics, and runtime;
• record that this was a one-time user-approved manual backfill;
• leave the daily automation instructions unchanged.

Failure Handling

The batch must not be pushed if:

• any topic has become duplicative or cannot support its full reader job;
• a high-stakes claim cannot be verified from a current primary source;
• a source conflict cannot be described conservatively;
• any hero is missing, corrupt, off-dimension, or non-compliant;
• internal links or routes fail;
• tests or build fail;
• unrelated workspace files enter the diff;
• the production branch cannot be updated safely;
• another active run is already pushing overlapping blog content.

If one topic fails its final demand, uniqueness, or official-source check, stop the batch and present a scored replacement candidate to the user. Do not silently change the approved portfolio, and do not force a thin article merely to preserve the table above. Any approved replacement must be added to this specification before implementation resumes.

If production verification reveals a serious post-push issue, report the commit and exact issue. Do not perform a destructive rollback without explicit user instruction.

Acceptance Criteria

The work is complete only when:

• all 13 previously empty dates have one unique, substantial post;
• every post and image meets the shared contract;
• the existing-coverage audit shows no material cannibalisation;
• all factual claims are traceable to current official sources;
• npm test, npm run build, and git diff --check pass;
• the scoped commits are pushed normally to the resolved production branch;
• the pushed commit is present on the remote production branch;
• live route checks succeed or a specific deployment delay is reported;
• automation queue and memory state are updated outside the repository;
• the original workspace's unrelated files remain preserved.