There are actually several questions here.
found binaries for architecture 'all': bin/curl lint_control_architecture_valid_contents
This means that you have included compiled binaries in the package (in this case bin/curl) but said that the package is architecture-independent in the package manifest (not specifying an architectures key in meta/package.yaml means it defaults to architectures: ["all"], resulting in Architecture: all in DEBIAN/control). You should update meta/package.yaml to include architectures: ["amd64"].
unknown entries in package.yaml: 'description,summary' lint_snappy_unknown
You have included properties in your meta/package.yaml that are not recognised, namely description and summary. You should remove those.
See the guide on package metadata for more details on what properties are allowed.
(MANUAL REVIEW) type 'framework' not allowed lint_snappy_type_redflag
and
security policy not found framework_policies
The link after the failure message tells you what you need to know here:
- Frameworks must always specify framework policy, otherwise the store will reject it
- Framework snaps will always trigger a manual review to ensure the framework policy has not changed. Alternatively, the first upload could require manual review, but subsequent uploads could be automatically approved if the security policy does not change
