feat: update configuration files to enhance permissions and streamline Docker setup

[narthanaj]

Pull Request Title

Related Issue

Description

copilot:summary

Type

• Bug Fix
• Feature Enhancement
• Documentation Update
• Code Refactoring
• Other (please specify):

Proposed Changes

Screenshots / Code Snippets (if applicable)

How to Test

Checklist

• The code compiles successfully without any errors or warnings
• The changes have been tested and verified
• The documentation has been updated (if applicable)
• The changes follow the project's coding guidelines and best practices
• The commit messages are descriptive and follow the project's guidelines
• All tests (if applicable) pass successfully
• This pull request has been linked to the related issue (if applicable)

Additional Information

copilot:walkthrough

---

Summary by cubic

Allows Docker Compose commands in local tooling and uses host networking during Docker builds for smoother development. Also removes an unnecessary experimental Next.js TLS setting.

• Refactors
  • .claude/settings.local.json: enable Bash(docker compose:*).
  • docker-compose.yml: set build.network to host to improve build reliability and access host resources.
  • apps/frontend/next.config.ts: remove experimental turbopackUseSystemTlsCerts.

^{Written for commit 90b7e44. Summary will update on new commits.}

[kiloconnect]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (3 files)

• .claude/settings.local.json
• apps/frontend/next.config.ts
• docker-compose.yml

[Copilot]

Pull request overview

This pull request modifies configuration files across Docker, Next.js, and Claude AI tooling to adjust permissions and remove experimental features. The changes include adding host network access to Docker builds, removing a Next.js experimental TLS certificate feature, and expanding Claude AI bash permissions.

Changes:

• Added network: host to Docker Compose build configuration
• Removed turbopackUseSystemTlsCerts experimental flag from Next.js config
• Added docker compose permission to Claude AI settings

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
docker-compose.yml	Adds host network access to build context (potential portability concern)
apps/frontend/next.config.ts	Removes experimental Turbopack TLS certificate system integration
.claude/settings.local.json	Adds Docker Compose V2 syntax permission (creates redundancy with existing hyphenated commands)

[Copilot]

The network: host directive in the build context is unusual and potentially problematic. This setting is meant for runtime containers, not build contexts. During the build process, Docker already has network access to download packages and dependencies from the internet without requiring host networking.

Adding network: host to the build context can:

1. Reduce build portability across different environments
2. Potentially expose the host network to build-time processes unnecessarily
3. Not work correctly on all platforms (e.g., Docker Desktop for Mac/Windows)

If you're experiencing network issues during the Docker build (e.g., npm install failures, apt-get update failures), the issue is likely related to DNS configuration or corporate proxies, which should be addressed differently. Consider removing this line unless there's a specific documented reason for requiring host network access during the build.

Suggested change

network: host

[Copilot]

This creates a redundant permission entry. The file already has Bash(docker-compose ps:*) and Bash(docker-compose logs:*) on lines 4-5, which use the hyphenated docker-compose command. This new entry uses the space-separated docker compose syntax.

While both syntaxes are valid (Docker Compose V2 uses docker compose without the hyphen), having both patterns is inconsistent. Consider either:

1. Standardizing on one syntax (preferably docker compose as it's the modern V2 syntax)
2. Updating all existing entries to use the same format
3. If you need both for compatibility, use a single wildcard like Bash(docker*compose*:*) to cover both syntaxes

[cubic-dev-ai]

No issues found across 3 files

---

Since this is your first cubic review, here's how it works:

• cubic automatically reviews your code and comments on bugs and improvements
• Teach cubic by replying to its comments. cubic learns from your replies and gets better over time
• Ask questions if you need clarification on any suggestion