Pilot Onboarding Batch Log¶
Date: 2026-06-25
Status: Ready execution log for EP10-T6. This does not complete EP10-T6 until real pilot landlords are accepted, onboarded, and measured.
Related pilot ops: Founding pilot ops
Related scorecard: Pilot scorecard
Related outreach list: Founding pilot outreach list
Related backlog: Pre-release delivery epics
Purpose¶
This log is the source of record for the first Founding Landlord Program onboarding batch.
Use it after outreach and interviews produce accepted pilot landlords. Do not count demos, seed data, internal test accounts, or founder-entered substitute work as activation evidence.
Batch 1 Status¶
| Field | Value |
|---|---|
| Batch status | not_started |
| Target landlord count | 3-5 |
| Accepted landlords | 0 |
| Kickoffs completed | 0 |
| Landlords with one real lease in product | 0 |
| Landlords with property setup complete | 0 |
| Landlords with lease setup complete | 0 |
| Landlords with one document/evidence artifact uploaded | 0 |
| Landlords with rent schedule or payment-follow-up workflow created | 0 |
| Landlords with three real target workflows completed | 0 |
| Current blocker | No real pilot landlords accepted yet. |
| Next Product Owner action | Contact EP10-T5 outreach targets and schedule landlord interviews. |
Batch Start Rule¶
Start Batch 1 only when all conditions are true:
- 3-5 landlords are accepted into the pilot
- every accepted landlord has a participant ID in the scorecard
- every accepted landlord has at least one real lease or transition event ready
- every accepted landlord has agreed to weekly check-ins
- no active support stop condition is open
- the Product Owner can attend every kickoff personally
If fewer than three accepted landlords are ready, continue interviews and do not start the batch. If more than five are ready, waitlist the excess until support load from the first batch is known.
Admin Intake Support¶
The web-admin Founding Pilot view shows a readiness strip above the applicant table. The first metric, applicants on page, is page-scoped; the remaining validation metrics come from the backend summary across all founding-pilot applicants:
- applicants on the current page
- 2-10 unit applicants
- real-lease confirmations
- batch-ready applicants
- accepted applicants
- accepted batch-ready applicants
- completed landlord interviews
- completed tenant interviews
- pilot batch records
- kickoff scheduled
- week 1 active
- paused/exited batch records
- batch landlord interviews
- batch tenant interviews
- batch pricing pilots
- batch pricing asked
- batch pricing accepted
- batch pricing rejected
- batch pricing missing
- batch rejected with objection
- batch rejected missing objection
- batch pricing acceptance
- memo matched users
- memo owner-only ready
- memo 3+ workflows
- memo tenant-task participants
- memo tenant-task completions
- batch outcomes recorded
- batch outcomes missing
- batch refused/churned
- batch support watch/stop
- batch P0/P1 incidents
- batch support hours
Each applicant row also shows a Pilot readiness label. A lead is Ready for
batch only when they are in the 2-10 unit band and confirmed willingness to
move a real lease. Use this as an operational filter before copying accepted
participants into the batch rows below.
Admin reviewers can now record per-applicant review state directly in the Founding Pilot table:
pilotDecision:ACCEPTED,WAITLIST,NURTURE,DECLINED, orNOT_FITlandlordScore: whole number from 0 to 10reviewNote: short internal review notereviewedAt: backend timestamp from the latest saved review
Use ACCEPTED only for landlords the Product Owner has approved for Batch 1.
Do not treat Ready for batch alone as acceptance evidence.
The admin list can be filtered by review decision. Use the ACCEPTED filter
as the source view for copying approved landlords into the participant rows.
Use WAITLIST, NURTURE, DECLINED, and NOT_FIT filters to keep non-batch
leads out of Batch 1 planning.
The Founding Pilot toolbar also has an action queue filter for finding the specific rows behind the aggregate readiness gaps:
Needs batch: accepted applicant has no saved Batch 1 statusNeeds interview: accepted applicant has no saved landlord interview timestampNeeds pricing: batched applicant still has no pricing responseNeeds post-pilot: pricing response exists but post-pilot next step is emptyNeeds outcome: post-pilot next step exists but final pilot outcome is emptyNeeds refusal blocker: refused or churned batched applicant is missing a blocker code or short outcome note
Use Needs batch while filling the Batch 1 rows. Use Needs interview before
starting or expanding Batch 1 so accepted applicants do not bypass the landlord
interview evidence gate. Use the other queues during pricing and memo closeout
so aggregate "missing" counters can be resolved at row level. After filtering a
queue, use Copy action queue to copy an
anonymized worklist with participant ID, queue reason, review decision, batch
status, pricing response, post-pilot next step, outcome, blocker code, and next
action. The queue snapshot excludes applicant names, emails, phone numbers,
free-form intake messages, review notes, and support case identifiers. The copy
action reloads every page in the selected queue before copying and includes a
Rows exported count, so a queue larger than the visible admin page is not
mistaken for a complete worklist.
Before acceptance, use the admin qualification counters and row details to prioritize applicants. The Founding Pilot admin view now shows global counts for self-managed applicants, artifact-ready applicants, pilot-committed applicants, and fully qualified applicants. A fully qualified applicant has 2-10 units, is self-managed or mixed-management, is willing to show real artifacts, can move a real lease, can activate two live units within 30 days, can join weekly check-ins, gives testimonial/case-study consent, and consents to pilot contact.
Admin reviewers can also record per-applicant Batch 1 execution state directly in the Founding Pilot table:
pilotParticipantId: anonymized participant ID, for examplePILOT-001pilotBatchStatus:ACCEPTED,KICKOFF_SCHEDULED,KICKOFF_DONE,WEEK_1_ACTIVE,THIRTY_DAY_ACTIVE,PAUSED, orEXITEDpilotBatchAcceptedAt: acceptance timestamppilotKickoffAt: kickoff timestamppilotFirstWorkflow: first target workflowpilotCurrentBlocker: current onboarding blockerpilotNextAction: next Product Owner actionpilotBatchRecordedAt: backend timestamp from the latest saved batch update
Use the admin row as the live operational source for per-applicant batch state. Copy only anonymized participant IDs and non-PII status notes into the docs rows below when preparing weekly reviews.
Admin reviewers can also record completed interview evidence directly in the Founding Pilot table:
landlordInterviewCompletedAt: landlord interview completion timestamptenantInterviewCompletedAt: tenant interview completion timestamp, only when tenant evidence is in scopepilotInterviewsRecordedAt: backend timestamp from the latest saved interview evidence update
Use these timestamps to reconcile the scorecard's completed landlord/tenant interview rows before starting or expanding Batch 1. Interview counts alone do not complete EP10-T6; they only prove that the pre-batch evidence is no longer being tracked manually.
The Founding Pilot toolbar includes Copy interview log, which copies an
anonymized Markdown snapshot from rows that have landlord, tenant, or recorded
interview timestamps. The snapshot includes participant ID, source row, city
band, unit-count band, batch status, landlord interview date, tenant interview
date, interview recorded date, and next action. It excludes applicant names,
emails, phone numbers, free-form intake messages, review notes, and interview
notes. Before copying, the admin reloads every page matching the active
founding-pilot filters and includes Rows exported, so interview
reconciliation is not capped to the visible admin page.
The Founding Pilot toolbar includes Copy batch log, which copies an
anonymized Markdown snapshot from the loaded batch rows. The snapshot uses only
participant ID, source row, city band, unit-count band, accepted date, kickoff
date, first workflow, batch status, current blocker, and next action. It
intentionally excludes applicant names, emails, phone numbers, free-form
messages, review notes, and other raw lead details. Before copying, the admin
reloads every page matching the active founding-pilot filters and includes
Rows exported, so Batch 1 reconciliation is not capped to the visible admin
page.
For accepted applicants that still have no saved Batch 1 status, Copy batch
log also includes the row with batch status empty. Use this from the
Needs batch queue so accepted-but-unbatched gaps remain visible in this log
instead of being omitted from the snapshot. Wrocław city values are normalized
to the wroclaw city band in copied snapshots.
Each applicant row also has an on-demand activation evidence control. Use
Evidence only after the accepted applicant has created or been matched to a
real app account. The control matches the intake email to an app user and shows
per-applicant counts for:
- matched app user and role
- owner-only activation readiness
- property setup
- active lease setup
- active rent schedule setup
- payment request and payment receipt evidence
- tenant invite evidence
- tenant task completions: accepted tenant invite, tenant handover confirmation/decline, tenant final-settlement confirmation/decline, tenant-authored lease message, tenant-uploaded evidence, or tenant-submitted support report
- handover evidence
- document/evidence uploads
- deposit/final-settlement evidence
- lease message and payment-reminder evidence
- in-app problem/support reports, including total, open, in-progress, resolved, and dismissed counts for the matched owner account plus tenant users linked to that owner's leases
- workflow-count categories with at least one real record
Copy only anonymized participant IDs and counts from this evidence into the Activation Log. Do not copy raw emails, user IDs, addresses, document names, rent amounts, or tenant data into this docs repo.
The Founding Pilot toolbar also includes Load evidence, which bulk-loads
activation evidence for all currently visible applicant rows that are not
already loaded. Use it when previewing activation evidence on the current
admin page. This uses the same per-row evidence endpoint and does not change
the anonymized snapshot fields copied into this docs repo.
Use Copy activation log to copy an anonymized Markdown snapshot for the
Activation Log. Before copying, the admin reloads every page matching the
active founding-pilot filters, loads missing per-row activation evidence, and
includes Rows exported, so activation reconciliation is not capped to the
visible admin page. The snapshot includes participant ID, property setup, lease
setup, document/evidence, rent schedule, payment proof, handover, tenant
invite, tenant task, issue report, deposit/settlement, message/reminder, and
total workflow count. The deposit/settlement and message/reminder cells are
measured by the activation evidence endpoint. Tenant invite is owner-created
invite volume; tenant task is tenant-side completion volume from the concrete
actions listed above. The cohort-level Memo 3+ workflows summary counter uses
the same
deposit/settlement and message/reminder workflow categories as the row-level
activation evidence, so the weekly review and final memo do not undercount
real pilot usage in those areas.
Participant Rows¶
Use participant IDs only. Keep names, emails, phone numbers, property addresses, rent amounts, lease details, bank details, and tenant data outside this docs file.
| Participant ID | Source row | City band | Unit count band | Accepted date | Kickoff date | First real workflow | Batch status | Current blocker | Next action |
|---|---|---|---|---|---|---|---|---|---|
PILOT-001 |
empty |
Awaiting accepted landlord. | |||||||
PILOT-002 |
empty |
Awaiting accepted landlord. | |||||||
PILOT-003 |
empty |
Awaiting accepted landlord. | |||||||
PILOT-004 |
empty |
Optional capacity slot. | |||||||
PILOT-005 |
empty |
Optional capacity slot. |
Allowed batch statuses:
emptyin this docs table only, when no admin batch status is saved yetACCEPTEDKICKOFF_SCHEDULEDKICKOFF_DONEWEEK_1_ACTIVETHIRTY_DAY_ACTIVEPAUSEDEXITED
Kickoff Checklist¶
Complete this checklist for every accepted participant.
| Step | Required evidence | Done |
|---|---|---|
| Confirm eligibility and no excluded workflow | Scorecard participant row has pilot_decision=accepted. |
|
| Confirm one real lease or transition event | Participant confirms artifact exists before kickoff. | |
| Confirm legal boundary | Participant accepts MamNajem does not provide legal advice. | |
| Confirm support channel | Participant knows in-app report and support email path. | |
| Create or allow account | Account is available for kickoff. | |
| Set up first property | Real property exists in product. | |
| Set up first lease or transition event | Real lease/transition event is represented in product. | |
| Add document or evidence artifact | At least one real artifact is uploaded or attached. | |
| Create rent schedule or payment-follow-up workflow | Schedule/reminder/follow-up exists in product. | |
| Decide tenant invite timing | Owner-only value path and tenant timing are recorded. | |
| Record first-week target | Next unit or workflow is recorded. | |
| Schedule weekly check-in | Date/time or written-update deadline is set. |
Activation Log¶
Count only real workflows.
| Participant ID | Property setup | Lease setup | Document/evidence | Rent schedule | Payment proof | Handover | Tenant invite | Tenant task | Issue report | Deposit/settlement | Message/reminder | Workflow count |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
PILOT-001 |
0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
PILOT-002 |
0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
PILOT-003 |
0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
PILOT-004 |
0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
PILOT-005 |
0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
Blocker Log¶
Use one row per onboarding blocker.
| Date | Participant ID | Blocker type | Severity | Product area | Owner | Resolution target | Status | Note |
|---|---|---|---|---|---|---|---|---|
| activation / tenant / support / legal / privacy / pricing / product / habit | P0 / P1 / P2 / P3 | open / closed |
Weekly Batch Review¶
Use this table before the weekly pilot review.
| Metric | Week 1 | Week 2 | Week 3 | Week 4 | Decision note |
|---|---|---|---|---|---|
| Accepted landlords | 0 | ||||
| Kickoffs completed | 0 | ||||
| Live units in product | 0 | ||||
| Landlords with owner-only activation | 0 | ||||
| Landlords with 3+ workflows | 0 | ||||
| Tenant task completions | 0 | ||||
| Support requests | 0 | ||||
| P0/P1 support items | 0 | ||||
| Price discussions completed | 0 | ||||
| Batch decision | continue / narrow / pause / stop |
EP10-T6 Completion Rule¶
EP10-T6 can be marked complete only when:
- Batch 1 has 3-5 accepted real pilot landlords, or the Product Owner documents why a smaller batch is the only supportable start
- each accepted landlord brings at least one real lease or transition event
- each accepted landlord completes property setup
- each accepted landlord completes lease setup
- each accepted landlord uploads at least one document or evidence artifact
- each accepted landlord creates a rent schedule or payment-follow-up workflow
- each accepted landlord completes at least three real target workflows during the pilot, or exits with an exact blocker reason
- blocker notes are recorded in this log and the scorecard
Evidence¶
This document is an EP10-T6 execution aid only. It records that Batch 1 is ready to run once real pilot landlords are accepted, but it does not claim the first pilot onboarding batch has happened.
Implementation support:
- backend integration commit
f42e9cfadds persistent applicant review state, the adminPATCH /v1/admin/founding-pilot-intake/{id}/reviewendpoint, OpenAPI contract, migration constraints, and integration coverage. - web-admin commit
f8c411badds Founding Pilot batch-readiness metrics and row-level readiness labels for the existing admin intake list. - web-admin integration commit
75fe580adds review controls, accepted-count metric, API client coverage, and admin app coverage for saving pilot review decisions. - backend integration commit
2babd1fand web-admin integration commita97825aadd review-decision filtering so the Product Owner can isolateACCEPTEDapplicants before filling Batch 1 participant rows. - backend integration commit
a17a79ealigns the cohort-level memo3+ workflowscounter with row-level activation evidence by including deposit/settlement and message/reminder workflow categories. - backend integration commit
3a14d26and web-admin integration commit63d8f20add batch-scoped outcome/support summary counters and memo rows for outcomes recorded, outcomes missing, refused/churned participants, support watch/stop status, P0/P1 incidents, and support hours. - backend integration commit
12de0d8and web-admin integration commit1dc76b7add a global Founding Pilot validation summary for Batch 1 readiness and pricing-test evidence. - backend integration commit
0fd5f95and web-admin integration commit0c74ae2add per-applicant activation evidence so the Product Owner can verify matched account, owner-only readiness, workflow counts, and blocker signals before copying anonymized counts into this log. - backend integration commit
3a5302cand web-admin integration commit41144ccextend that evidence with in-app support-load status counts for the matched owner account and linked tenant accounts. - backend integration commit
198b293and web-admin integration commit9a6ac48add admin outcome/support fields for copying the reviewed support log into the intake entry: final outcome, refusal/churn blocker, P0/P1 counts, support hours, and support status. - backend integration commit
5f5ee63and web-admin integration commit8eb3ad8add persistent per-applicant Batch 1 state, the adminPATCH /v1/admin/founding-pilot-intake/{id}/batchendpoint, OpenAPI contract coverage, admin summary counters for batch status, and web-admin controls for participant ID, status, accepted/kickoff timestamps, first workflow, blocker, and next action. - web-admin integration commit
70ebd60addsCopy batch log, an anonymized Markdown snapshot action for the loaded Founding Pilot batch rows, so Batch 1 docs rows can be updated from participant IDs, city/unit bands, dates, workflow, status, blocker, and next-action fields without copying applicant PII. - web-admin integration commit
15eb1cfmakesCopy batch loginclude accepted applicants that do not yet have a saved Batch 1 status asemptyrows, and normalizes Wrocław to thewroclawcity band, soNeeds batchgaps can be copied into this log without applicant PII. - web-admin integration commit
5f3de7daddsCopy activation log, an anonymized Markdown snapshot action for loaded per-applicant activation evidence, so Activation Log rows can be copied from participant IDs and measured app-backed counts without copying applicant PII or matched user IDs. - web-admin integration commit
d43ccacaddsLoad evidence, a toolbar action that bulk-loads activation evidence for visible Founding Pilot rows beforeCopy activation log, so batch reconciliation no longer requires clickingEvidenceon every row. - web-admin integration commit
5fd6e6emakesCopy activation logreload every matching founding-pilot page, load missing activation evidence, and addRows exported, so Activation Log rows are not capped at the visible admin page. - backend integration commit
81f24bcadds measured deposit/settlement and message/reminder counters to per-applicant activation evidence and includes those categories in the activation workflow count. - web-admin integration commit
f039241exports those measured deposit/settlement and message/reminder counts inCopy activation logsnapshots while retainingnot_measuredas a fallback for older backend responses. - backend integration commit
d2529edand web-admin integration commit6f6f2beadd tenant-task completion counts to row-level activation evidence, splitCopy activation loginto separate tenant invite and tenant task columns, and add memo tenant-task participant/completion counters. - backend integration commit
2dd46e4and web-admin integration commit8cc0ecfadd the Founding Pilot action queue filter so the Product Owner can isolate rows that need batch, pricing, post-pilot, outcome, or refusal blocker follow-up. - backend integration commit
4e794beand web-admin integration commit36bc273add theNeeds interviewaction queue so accepted applicants missing landlord interview evidence can be isolated before Batch 1 starts or expands. - web-admin integration commit
07d4e13addsCopy action queue, an anonymized Markdown snapshot for the selected Founding Pilot action queue. It copies participant ID, queue reason, review decision, batch status, pricing response, post-pilot next step, outcome, blocker code, and next action without applicant PII or support case identifiers. - web-admin integration commit
0bbbd74makesCopy action queuereload all pages for the selected action queue at the backend's 100-row page cap and addRows exportedto the snapshot, so copied worklists are not limited to the visible admin page. - web-admin integration commit
34550f3makesCopy batch logreload every matching founding-pilot page at export size and addRows exported, so Batch 1 logs are not capped at the visible admin page. - backend integration commit
cd5a697, backend coverage follow-upc6d1406, and web-admin integration commit39b5d29add row-level landlord/tenant interview timestamps, global completed-interview counters, Batch 1 completed-interview counters, and admin controls for saving interview evidence. - web-admin integration commit
60ee151addsCopy interview log, an anonymized full-export snapshot for row-level landlord/tenant interview evidence.
Deployment evidence:
- backend pipeline
2629703531succeeded forf42e9cfonintegration. - web-admin pipeline
2629716193succeeded for75fe580onintegration. - backend pipeline
2629749586succeeded for2babd1fonintegration. - web-admin pipeline
2629758524succeeded fora97825aonintegration. - backend pipeline
2630258855succeeded for81f24bconintegration. - web-admin pipeline
2630268247succeeded forf039241onintegration. - backend pipeline
2631162540succeeded ford2529edonintegration. - web-admin pipeline
2631162539succeeded for6f6f2beonintegration. - backend pipeline
2631380073succeeded for2dd46e4onintegration. - web-admin pipeline
2631380022succeeded for8cc0ecfonintegration. - backend pipeline
2631782983succeeded forc6d1406onintegration. - web-admin pipeline
2631761550succeeded for39b5d29onintegration. - backend pipeline
2632706952succeeded for4e794beonintegration. - web-admin pipeline
2632706932succeeded for36bc273onintegration. - web-admin pipeline
2631853329succeeded ford43ccaconintegration. - web-admin pipeline
2631905926succeeded for15eb1cfonintegration. - web-admin pipeline
2632108038succeeded for34550f3onintegration. - web-admin pipeline
2632137296succeeded for5fd6e6eonintegration. - web-admin pipeline
2632684605succeeded for60ee151onintegration. - AWS Amplify job
52succeeded for39b5d29on theintegrationadmin branch. - AWS Amplify job
54succeeded ford43ccacon theintegrationadmin branch. - AWS Amplify job
56succeeded for15eb1cfon theintegrationadmin branch. - AWS Amplify job
62succeeded for34550f3on theintegrationadmin branch. - AWS Amplify job
63succeeded for5fd6e6eon theintegrationadmin branch. - AWS Amplify job
64succeeded for60ee151on theintegrationadmin branch. - AWS Amplify job
65succeeded for36bc273on theintegrationadmin branch. - Integration smoke loaded
https://integration.mamnajem.pl/v1/subscriptions/plansthroughagent-browserand confirmed the protected review route returns401without admin auth. Full review-form verification requires admin credentials. - Integration smoke loaded
https://admin-integration.mamnajem.pl/#founding-pilotthroughagent-browserand reached the admin sign-in screen. Full review-form verification requires admin credentials. - Integration smoke loaded
https://admin-integration.mamnajem.pl/?v=f039241b#founding-pilotthroughagent-browser, confirmed the deployed admin bundle containsdepositSettlementCount,messageReminderCount,deposit/settlement item, andmessage/reminder item, and confirmed the protected activation evidence route returns401without admin auth. - Integration smoke loaded
https://admin-integration.mamnajem.pl/?v=6f6f2be#founding-pilotthroughagent-browser, confirmed the deployed admin bundle containstenantTaskCount,Memo tenant-task participants,Memo tenant-task completions,Tenant task completions, and the splitTenant invite | Tenant tasksnapshot header, and confirmed the protected backend summary route returns401without admin auth. - Integration smoke loaded
https://admin-integration.mamnajem.pl/?v=8cc0ecf#founding-pilot, confirmed the deployed admin bundle containsFounding pilot action queue, all five action labels, andpilotAction, and confirmed the protected backend list route withpilotAction=NEEDS_PRICINGreturns401without admin auth. - Integration smoke loaded
https://admin-integration.mamnajem.pl/?v=39b5d29-browser#founding-pilot, confirmed the deployed admin bundleindex-CLFya2Pu.jscontainsSave pilot interviews,Completed landlord interviews,Batch landlord interviews, and the/interviewsAPI path, and confirmed the protected backend summary route returns401without admin auth. - Integration smoke loaded
https://admin-integration.mamnajem.pl/?v=d43ccac-browser#founding-pilot, reached the admin sign-in screen, confirmed the deployed admin bundleindex-_jUIho0J.jscontainsLoad activation evidence for visible pilots,Loaded activation evidence for, andCopy activation log, and confirmed the protected backend summary route returns401without admin auth. - Integration smoke loaded
https://admin-integration.mamnajem.pl/?v=15eb1cf-browser#founding-pilot, reached the admin sign-in screen, confirmed the deployed admin bundleindex-hCfaL1PJ.jscontainsCopy batch log,Pilot Batch Log Snapshot,empty, the accepted-row predicate, andwroclaw, and confirmed the protected backend summary route returns401without admin auth. - Integration smoke loaded
https://admin-integration.mamnajem.pl/?v=34550f3-browser#founding-pilot, reached the admin sign-in screen, confirmed the deployed admin bundle containsCopy batch log,Pilot Batch Log Snapshot,Rows exported:,Batch status, andCurrent blocker, and confirmed the protected backend list route returns401without admin auth. - Integration smoke loaded
https://admin-integration.mamnajem.pl/?v=5fd6e6e-browser#founding-pilot, reached the admin sign-in screen, confirmed the deployed admin bundle containsCopy activation log,Pilot Activation Log Snapshot,Rows exported:,Deposit/settlement,Message/reminder, andactivation-evidence, and confirmed the protected backend list and activation-evidence routes return401without admin auth. - Integration smoke loaded
https://admin-integration.mamnajem.pl/?v=60ee151-browser#founding-pilot, reached the admin sign-in screen, confirmed the deployed admin bundle containsCopy interview log,Copy founding pilot interview log snapshot, andPilot Interview Log Snapshot, and confirmed the protected backend summary route returns401without admin auth. - Integration smoke loaded
https://admin-integration.mamnajem.pl/?v=36bc273-browser#founding-pilot, reached the admin sign-in screen, confirmed the deployed admin bundleindex-BpjH9HBy.jscontainsNEEDS_INTERVIEW,Needs interview, andAccepted applicant is missing landlord interview evidence, and confirmed the protected backend list route withpilotAction=NEEDS_INTERVIEWreturns401without admin auth.