Development guide

Choose the customer baseline first

Do not start from repository default branches. Select a row in customer variants and check out its niseCore, WBF and include refs. Use its WBF customer_project, EWDK and target.

Change paths

• Core algorithms/device behavior: niseCore modules and public common/include contracts.
• Windows lifecycle/adapters: WBF wbdi/driver and adapters/synaFpAdapter.
• Customer features/package: WBF CustomerProjects/<name> and build properties.
• Firmware ABI: biometrics-include; requires cross-repository compatibility review.
• Delivery: driver-build workflows/actions and matrix.
• Focused tests: utest dev, using exact target ref and variant.

Safe sequence

1. State the affected customer rows and branches.
2. Identify interfaces and both sides of every changed cross-repo contract.
3. Update focused utest specs/assertions where behavior changes.
4. Run local/focused tests, then exact customer build.
5. Validate package/signing/driver tests appropriate to the change.
6. Record exact SHAs and remaining evidence gaps.

Generated and derived content

utest extracts target functions and generates/overrides headers at run time. Do not treat generated target.c or copied variant files as canonical production source.