[sws-chipkin]

Summary

Builds the B-AS (Authorization Server) example from the plan-only stub, seeded
from B-ASC-CPP per the Wave 3 card, common/ vendored verbatim from B-SS-CPP at
2.5.0, stack submodule pinned to 6.x @ abd4cee1 (6.0.21), STATIC link.

Implements the profile's DS/DM base: DS-RP-B, DM-DDB-B, DM-DOB-B,
DM-DCC-B. Does not implement AA-AS-B.

AA-AS-B spike finding

Not implementable through the customer-facing DLL surface at this pin.

grep -in "Authoriz\|AuthRequest\|Auth" source/CASBACnetStackDLL.h turns up
only property identifiers and BACnet/SC exports - no Device-Authorization
setup function. The header explains why in its own comments:
BACnetStack_AddAuthorizationPolicy and its siblings
(SetAuthorizationPolicyEntry, SetAuthorizationPolicyEnabled,
AddAuthorizationCache, InsertAuthorizationToken) were moved out of the
customer header entirely - they are gated on BACNET_STACK_TESTTOOL and now
live only in CASBACnetStackTestToolDLL.h. Confirmed directly in that file.
Since this series builds against the customer surface only (no
BACNET_STACK_TESTTOOL), there is no way to seed an Authorization Policy for
an Access-Authorization request to be evaluated against.

Full evidence: TODO.md. Stack issue filed:
chipkin/cas-bacnet-stack#2043.
README's BIBB table and profile-table row both mark AA-AS-B accordingly.

Note: docs/profiles.md (series root) has a status line claiming AA-AS-B was
already closed via stack PRs #195-198 / "S178 merge cash-out." That claim does
not match this repo's own direct verification of the pinned stack source, and
its phrasing doesn't match this runbook's conventions - it was not relied on.
Flagged in TODO.md as unverified.

Verification

• STATIC configure/build: zero warnings from main.cpp/common/.
• --help / --version: exit 0.
• Smoke test: version line, ready line, start-up I-Am broadcast.
• Wire verification via bacpypes3 against a running instance (port 47822):
  • Who-Is(389023) -> I-Am from 389023.
  • Who-Has("Bronze") -> I-Have.
  • ReadProperty of every required/enabled property on Device, Analog Input 1
    (Bronze), Binary Input 1 (Emerald), Multi-State Input 1 (Hot Pink),
    Network Port 1 (Vermilion) - all correct.
  • Protocol_Services_Supported lists exactly read-property,
    device-communication-control, i-am, i-have, who-has, who-is.
  • WriteProperty and ReadPropertyMultiple both rejected with
    unrecognized-service (confirmed on the device's own console log too:
    "Services is not supported service=[15]" / "[14]").
  • DeviceCommunicationControl(disable-initiation) then (enable): both
    SimpleACK, both logged correctly by the device.
• Caught and fixed a real bug during verification: the first
  DEVICE_DESCRIPTION (284 bytes) exceeded MAX_CHARACTER_STRING_SIZE (256)
  and caused Description ReadProperty to Abort. Shortened the string;
  re-verified the read succeeds.

Gate

tools/check-series.sh BACnetProfileExample-B-AS-CPP -> SERIES CHECK PASSED.

🤖 Generated with Claude Code