abcd capture's --source enum has no value for a security advisory (an external reviewer's finding on the forge) nor for a handover item (a NEXT.md or lab finding another session left for filing); the autonomous run used review-followup and agent-observation and stated the real origin in each body. Either the enum gains security-advisory and handover, or the surface page documents the mapping so every future run chooses the same values.

abcd capture's --source enum has no value for a security advisory (an external reviewer's finding on the forge) nor for a handover item (a NEXT.md or lab finding another session left for filing); the autonomous run used review-followup and agent-observation and stated the real origin in each body. Either the enum gains security-advisory and handover, or the surface page documents the mapping so every future run chooses the same values.

Remedy grounds (2026-09-29)

• The list lives once in internal/core/issueschema/issueschema.go:180-187, so either answer is one edit there or one table beside the flag's documentation, never a second vocabulary.
• Rejected: deciding the vocabulary here, which is the product thinker's ruling; the sibling record carries the same fork for autonomous-hunt and is ruled with it.